Workflow Run History And Troubleshooting
Workflow history helps administrators and managers understand what happened after an automated rule ran. Use it to confirm successful actions, review failures, and decide whether a workflow needs to be retried, paused, or updated.
What To Check In Run History
- Trigger: The event that started the workflow, such as low stock, overdue approval, delayed order, or a manual run.
- Conditions: The rules the workflow checked before continuing.
- Actions: The notifications, tasks, approvals, messages, or record updates the workflow attempted.
- Status: Whether the run completed, failed, is waiting, or needs attention.
- Timeline: The order of steps, timestamps, and any visible error messages.
Common Issues
- No run appears: Confirm the workflow is active and the triggering event actually happened.
- Conditions did not pass: Review the field values on the related record and compare them with the workflow rules.
- Notification not received: Check the recipient rule, user role, department, email, phone number, and notification preferences.
- Approval did not route: Confirm approvers have the correct role and the request meets the approval criteria.
- Repeated failures: Pause the workflow if it is creating noise, then correct the rule, action, or recipient setup before enabling it again.
Tip: When reporting a workflow problem, include the workflow name, related record, time it happened, expected result, and what appeared in the run history.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.