Automation Flows lets you build multi-step, multi-integration business processes. When a flow fails or behaves unexpectedly, the Governance area gives you visibility into what happened so you can diagnose and resolve issues on your own.
This article explains how to review flow executions, read the details of a single execution, and resolve the most common issues.
- Accessing Governance
- Flow Executions list
- Execution details
- What each component shows
-
Common issues and how to resolve them
- A flow execution shows an Error status
- Reference Table Lookup follows the Error exit
- Reference Table Update follows the Error exit
- Execute Action fails or times out
- An API triggered flow does not start, or the API call fails
- A Webhook trigger does not fire
- Get Context returns no data
- A Wait step does not behave as expected
- A Split Flow always takes the fallback exit
- A Functions step follows the Error exit
- A variable is not available in a step
- Related Articles
Accessing Governance
To review flow executions, open Automation Flows, click on a Flow, and review the Executions section
Flow Executions list
The flow executions list shows all flow executions from the last 20 days.
In the executions list, you can see:
- Date: The execution start time
- Status: The outcome of the execution (completed or failed).
- Execution ID: The unique identifier of the execution.
- Interaction ID: The unique identifier of the interaction related to this execution, if there is one.
- Duration: How long it takes for this execution to follow its course within the flow.
- Trigger: Which trigger started the execution (for example, through a time or event trigger).
You can also filter the executions based on the date of the execution, the trigger type that started the execution, the status, and the interaction ID. You can also search executions by Execution ID.
Execution details
Select an execution to open its details. The details view is organized into three parts.
Inside each execution detail, you can see information about the flow, such as the version in which this execution happened and the created and last modified dates. You can also see some generic details of the execution, such as the status, ID, duration, start and end time.
Execution drill-down
The drill-down shows the complete path the flow took, so you can inspect each step. Depending on the component, a step can show:
- Input: The values the step received, available as JSON and as a UI-friendly key match.
- Output: The values the step produced, available as JSON and as a UI-friendly key match.
- Execution time for the step and any messages or error details (for example, the response of an HTTP request).
- The exit the step followed (for example, Success or Error).
What each component shows
Use this table to know what to expect when you open a step in the drill-down.
| Component | Input | Output | Exits |
|---|---|---|---|
| Talkdesk Event Trigger | Event field values | — | Success · Error |
| APITrigger | Request input values (resolved parameters actually sent) | — | Success · Error / Timeout |
| Time-based Trigger (Scheduler) | Schedule configuration | Scheduled run details | Success · Error |
| Webhook Trigger | Incoming request values | — | Success · Error |
| Execute Action | Mapped input fields and the final request sent to the external system | The action response and output fields, when available | Success · Error / Timeout |
| Get Context | Mapped input fields at runtime | Context values retrieved | Success · Error / Timeout |
| Functions | Mapped input fields at runtime | Function response and output fields | Success · Error / Timeout |
| Reference Table Lookup | Selected table and lookup keys/values | Matched row columns exposed as variables | Success · Error |
| Reference Table Update | Selected table and mapped column values | Insert result | Success · Error |
| Split Flow | Conditions evaluated and their input values | The result of each condition and the path taken | One exit per condition · Fallback exit |
| Wait | Configured duration or target date/time | — | Success |
| AI Agent | Mapped input fields at runtime | The agent response and output fields | Success · Error / Timeout |
| End Flow | — | — | — |
Common issues and how to resolve them
A flow execution shows an Error status
Open the execution and use the drill-down to find the step that followed its Error exit. Review that step's Output and message/error details to see exactly what failed, then apply the relevant guidance below.
Reference Table Lookup follows the Error exit
This happens when the lookup key value is blank or null, or when no row matches the configured filters. It can also happen if the Reference Hub table is no longer available or you do not have access to it.
- Make sure the mapped key has a value at runtime. Add a Split Flow before the lookup to handle empty values.
- Confirm the Reference Hub table exists and is accessible to your account.
- Check Reference Hub limits: 1,000 rows, 100 columns, and 4 URL-type fields per table.
Reference Table Update follows the Error exit
The most common cause is that the table has reached its 1,000-row limit, or the table is no longer available.
- Use the row-usage indicator to check capacity, and delete unused rows or contact Support if the table is full.
- This component inserts a single row per execution (Add only). Update, upsert, and delete are not supported.
Execute Action fails or times out
- Only Connections actions are supported, and only actions from installed and active integrations are listed.
- Confirm all required inputs are mapped and review the external system's response in the step Output.
- For transient failures, configure the step's Retry & Timeout tab. See Talkdesk Automation Flows: Configuring Retry and Timeout.
An API triggered flow does not start, or the API call fails
- The API trigger is asynchronous only. The API response confirms whether the flow was triggered, not the flow's result.
- Requests are limited to 10 requests per second.
- Make sure the required OAuth scopes are included in your client configuration.
A Webhook trigger does not fire
- The webhook only starts the flow when it receives a correctly signed request.
- Verify the signing key and confirm the external system is calling the flow's webhook URL.
Get Context returns no data
- Only interaction context is available, and only when the flow receives the Interaction ID.
- The context must be exposed to Conversations & Automations in your Studio configuration.
- If a duplicated field is configured, that field is not saved - check for duplicates.
A Wait step does not behave as expected
- A flow can be paused for up to 30 days. For longer delays, restructure the flow.
A Split Flow always takes the fallback exit
- Conditions are evaluated in exit order; the flow takes the first exit whose conditions are met, otherwise the fallback exit.
- Review the operators and values, and confirm every exit (including the fallback) is connected to a subsequent step.
A Functions step follows the Error exit
- Check the JavaScript for runtime errors and confirm at least one output is defined (required).
A variable is not available in a step
- You can only map variables from previous steps. Each component's outputs are automatically exposed as variables to downstream steps.