Approval Process Execution Logs
Execution logs show how one published approval process handled related-form records. They help administrators locate the current node, approver, decision path, blocked step, or callback state without changing the process definition.
From Approval Process Management, choose Execution logs on a process.
Before You Look At Logs
- Logs belong to one process: open the process first, then its execution logs
- Every instance keeps the version and runtime snapshot it started with, so changing the process later does not rewrite existing entries
- Use logs to answer three questions: where the instance is now, who owns the current task, and why it stopped
Log List
The page supports keyword search, status filtering, manual refresh, and pagination. Search matches business records, initiators, nodes, and current approvers, and the status filter provides the most common runtime states: pending, approved, rejected, returned, blocked, and canceled.
| Column | Description |
|---|---|
| Business record | Related-form record processed by the approval instance |
| Initiator | Member or actor that started the instance |
| Status | Current or final approval instance result |
| Current node | Node currently waiting or processing |
| Current approver | Current approval task owner when available |
| Started at | Time the instance started |
| Completed at | Time a terminal result was recorded |
| View | Opens execution details |
Execution Status
Depending on the current node and user action, the instance status can be:
| Status | Meaning |
|---|---|
| Waiting | The instance started and is waiting for a decision, a service, or a callback |
| Pending approval | The instance is at an approval node, waiting for an approver |
| Approved | The approval node was approved and the process continues on the approved route |
| Rejected | The approval node was rejected and the instance finished with that outcome |
| Returned | The approval node was returned and the instance finished with that outcome |
| Withdrawn | The initiator withdrew the instance while it was pending at the current approval step |
| Completed | The process reached the end node |
| Blocked | The node could not continue, for example because an approver, script, integration flow, or runtime dependency was unavailable |
| Canceled | The instance was canceled |
Execution Detail
Choose View to open the execution detail drawer:
| Section | Description |
|---|---|
| Basic information | Instance ID, record, initiator, status, start and completion time, duration, and the runtime error or block reason |
| Approval flow execution | Read-only graph showing node execution state and decision outcomes |
| Business snapshot | JSON snapshot of the related-form record captured for this instance; the JSON can be copied |
Execution Graph
| Display | Meaning |
|---|---|
| Pending | The node is currently active, waiting for a decision, a service completion, or a callback |
| Completed | The node finished normally; approval and branch nodes can also display their recorded outcome |
| Blocked | The node could not continue, for example because an approver, script, integration flow, or runtime dependency was unavailable |
| Canceled | Execution at the node was canceled |
| Not run | The node exists in the published graph but was not part of this instance's route |
| Highlighted connection | Both endpoint nodes have a recorded runtime state; it is animated while the instance is pending |
| Dashed connection | At least one endpoint node has not run in this instance |
Branch nodes show matched or unmatched outcomes, and approval nodes show approved, rejected, or returned outcomes when they are recorded.
Troubleshooting Order
- Search by business record or initiator
- Check the instance status and current node
- Open the detail drawer and locate the last pending, blocked, or completed node in the graph
- Read the error or block reason in the basic information
- Compare the business snapshot with the trigger and condition configuration in the design canvas
- For approval nodes, confirm the primary or fallback approvers can be resolved
- For service calls, confirm the Studio script or service-call integration flow is still published and available
- For wait callbacks, confirm the selected inbound webhook flow is published and the external request uses the rendered correlation key and the callback contract
- Adjust the process, publish a new version, and test with a new record event; existing instances keep their original version snapshot
Troubleshooting
| Symptom | What to check |
|---|---|
| There are no logs at all | The process may never have been triggered: check the trigger configuration and whether the record change matched it |
| The current approver is empty | The node could not resolve an approver; open the detail drawer and read the blocked reason |
| The instance stays pending for a long time | A service call or wait callback may still be waiting; check the last pending or blocked node and its error |
| The process took an unexpected branch | Compare the business snapshot with the values and operators of that branch node |
| An older entry differs from the current design | The instance kept its original version snapshot; open that version from version history to compare |