Skip to content
Workflows

Inspect workflow runs and restore a previous version

Use execution history to diagnose behavior and version history to recover a configuration.

CCorthex product guidesUpdated October 15, 20262 min read
Where to find itWorkflows → runs / version history

Before you begin

Open Workflows in the workspace navigation. Decide which event should start the flow and which agents should receive it. Start with an unpublished draft.

Example workspace · Demo data. Compare expected results with the trace, then verify in a real channel. Select the image to enlarge it.
Workflow test controls and simulated context

Example workspace · Demo data. Compare expected results with the trace, then verify in a real channel. Select the image to enlarge it.

Step by step

  1. 1

    Find the relevant run

    Match the time, agent and conversation. Inspect the trigger, decision trace and action outcome.

  2. 2

    Explain the decision

    Check the exact inputs and condition that selected a branch. Distinguish validation, provider and delivery errors.

  3. 3

    Open a previous version

    Use the available version history when a recent configuration was better. Review what will be restored.

  4. 4

    Restore as a draft

    A restored version must be reviewed and published again before replacing live steps. Retest assignments and the affected scenario.

Good to know

Run history is diagnostic evidence, not a promise that every external system completed a business process. Version retention is limited; export important reviewed configurations.

Check the result

Test matching, non-matching and missing-data cases. Review the publication, publish the steps and save the intended agent assignments.

Questions & troubleshooting

Can undo retract an action already delivered?

No. Builder undo changes configuration. It does not unsend a visitor message or reverse an external business action.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.