Monitor workflow runs to see whether published agentic workflows are starting, progressing, completing, or failing for employees.
A workflow is the published process definition. A workflow run is one execution of that definition, with its own progress, status, data, and history.
For more information, see Understand workflow runs.
Before you begin
Make sure you have:
- The Experience Designer or Tenant administrator role.
- At least one published (Live) workflow.
- Access to the workflow designer and run history for your tenant.
Open workflow runs
- From Applaud admins, select Workflows.
- Open the workflow you want to inspect.
- Select the run you want to view.
In Run mode:
- The canvas is read-only.
- Actions show execution status.
- You can inspect results, outputs, and conversation details for actions that interacted with the employee.
- Long-running actions, such as waits, show their current status.
Viewing a run doesn't change the workflow definition.
What to check for each run
Review the following areas:
| Area | What to look for |
| Run status | Whether the run is in progress, waiting, completed, canceled, timed out, or failed. |
| Progress/steps | Whether employee-facing milestones advanced as designed. |
| Start | Whether the run began from the expected user-initiated or event-based trigger. |
| Agent actions | Whether required outputs were captured and tools were used as expected. |
| Run Tool actions | Whether mappings succeeded and the external system returned the expected result. |
| Waits/events | Whether the run is paused for employee input or an external event. |
| Errors | The first action that failed and the error detail. |
Common monitoring scenarios
The employee says nothing started
- Confirm that the workflow is Live.
- Confirm that the managed start tool is attached to the assistant. See Publish a workflow and attach the start tool.
- Search run history for a run around the time of the request.
- If no run exists, the assistant likely never started the workflow. Retest with a clearer prompt and verify the tool attachment.
If no workflow run exists, focus on the Start configuration, managed start tool, and assistant configuration. If a run exists, inspect the run to determine where the workflow stopped.
The run is waiting
A waiting run may be normal. Check whether the workflow is:
- Waiting for an employee reply in an Agent action.
- Waiting for an approval or external event.
- Waiting for a scheduled time.
Don't republish to "unstick" a waiting run unless the design itself is wrong. Fix the draft for future runs; decide separately how to handle the in-progress run.
The run failed
- Open the run and identify the first failed action.
- Correct the workflow draft, such as instructions, mappings, tool configuration, or conditions.
- Confirm that dependent tools are still Active and eligible for the action type.
- Publish a new version.
- Test with a new run.
Versions and in-progress runs
- New runs use the latest published version.
- Runs already in progress continue on the version they started with.
- Publishing a fix doesn't rewrite history for earlier runs.
For more information, see Understand workflow versions.
Operational tips
- Monitor new workflows closely after go-live.
- Watch for repeated failures on the same action - usually a mapping, tool eligibility, or instruction issue.
- Separate "assistant didn't start the workflow" problems from "workflow started but an action failed."
- Use test runs after each publish before broad employee rollout.