Even well designed workflows can run into issues during testing or after they have gone live.
The good news? Most problems aren’t caused by a broken workflow. They’re usually caused by a small configuration detail that’s easy to overlook.
Before rebuilding your process, walk through these common troubleshooting steps.
💧 Process stuck? Check your process rules.
When a workflow won’t move to the next step, the process rules are one of the first places to look.
Common issues include:
- AND vs. OR logic
- Rules that aren’t grouped correctly
- Conditions that can never be met
One small rule can prevent an entire workflow from moving forward.
🤔 The task is assigned, but the user can’t find it anywhere.
If a user says they don’t have a task, don’t assume it’s missing.
Start by checking:
- Is it assigned to the correct user or group?
- Does the user have the proper role or permissions?
- Is the task being filtered out of their task list?
- Is the process in the correct publish status?
Most of the time, the task is exactly where the workflow says it should be.
🤔 A task in my process keeps failing.
If a task repeatedly fails, look at the Request Details for the error message before making configuration changes.
Then verify that:
- all required settings have been configured
- any integrations are returning the expected data
- the task has everything it needs to execute successfully
Error messages usually point you in the right direction.
🤔 What Would Danielle Do?
When something isn’t working, don’t assume the workflow is broken.
Start with the configuration.
A few minutes spent checking rules, assignments, permissions, and task settings can save hours of unnecessary troubleshooting.