Publishing changes and investigating common issues

Publishing makes a workflow version available to new customer sessions on a short code. Saved edits remain in draft until the workflow is published.

Use this guide when you are ready to release workflow changes.

Before publishing

Confirm that:

• The workflow has been saved.
• A short code is assigned.
• The workflow has been tested.
• The first menu is correct.
• All required menu paths are connected.
• Dynamic menus have been tested with realistic data.

Publishing requires a short code. If a workflow does not have one, assign it before publishing.

Publish a workflow

Open the workflow in the builder and publish the current draft.

During publishing, include a short change summary. The summary should explain what changed in plain language, such as:

• Added airtime purchase path.
• Updated welcome screen copy.
• Changed balance enquiry routing.
• Fixed account selection menu.

The summary appears in version history and helps the team understand what each published version introduced.

What happens after publishing

When publishing succeeds:

• A new published version is created.
• The workflow status is updated.
• New customer sessions use the published workflow.
• Existing customer sessions are not interrupted.

Use version history to review previous published versions.

Common publishing issues

Short code is missing

Publishing requires a short code.

Assign an available short code to the workflow, save the workflow, and publish again.

Short code is already in use

Only one published workflow can use a short code at a time.

If another published workflow already uses the selected short code, choose a different short code or unpublish/change the other workflow according to your team's release process.

Workflow graph is invalid

The workflow graph must be valid before it can be published.

Check for:

• Missing first menu.
• Options that do not route to a next screen.
• Menus that should be terminal but are still expecting another step.
• Dynamic menus without valid configuration.

Fix the issue, save, and publish again.

Workflow compile validation failed

Compile validation checks whether the workflow can be converted into a runnable USSD journey.

Review the validation message, then check the affected menu, option, request, or dynamic template. After making changes, save and publish again.

Dynamic source test failed

If a dynamic menu cannot fetch or map options correctly, customers may not receive the expected choices.

Check:

• URL and method.
• Headers and parameters.
• Request body.
• Template item path.
• Template value and label paths.
• Any variables taken from earlier customer input.

Run the dynamic source test again before publishing.

After publishing

After a release, monitor sessions for the workflow.

Look for:

• Failed or abandoned sessions.
• Unexpected exit points.
• Dynamic menus returning no options.
• More hops than expected.
• Customer paths that do not match the intended journey.

If you need to make a correction, edit the workflow draft, test it, and publish a new version with a clear change summary.