Reference
Fix workflow and Connection problems
Check a workflow that is not ready, a failed run, or a Connection test that does not pass.
Start with what you see
Choose the closest problem
Select one symptom. You will still check the evidence before changing anything.
What you see
- The workflow draft says it needs attention or cannot be published.
- A run stays waiting or ends as failed.
- A Connection test fails.
- A Connection test passes but the workflow operation fails.
What it means
A draft must pass its checks before it can be published. A run keeps the exact workflow version and events used for that attempt.
A Connection test proves only that the saved Connection worked for its test at that time. The workflow may need another remote action or different information.
Likely causes
- A required step, input, link, or setting is missing from the draft.
- The run is waiting for work, approval, a service, or a safe retry.
- The remote address, port, sign in method, secure connection setting, or network rule is wrong.
- The remote account does not allow the exact operation.
- The Connection was changed after the workflow version was published.
- The person or Workflow service lacks the exact Run or resource action.
Safe checks
- Run Check readiness on the draft and read every issue.
- Confirm the run uses the expected published version.
- Find the run in Operations and record its state and run ID.
- Read the first matching failure in Operational logs.
- Test the saved Connection once.
- Check its address, secure connection choice, and allowed network without showing its secret.
- Use Check access for the exact workflow or remote resource action.
Solutions
- Correct each reported draft issue, then check the draft again.
- Publish a new version only after a safe draft test passes.
- Correct the identified Connection or network setting, then test once more.
- Ask the remote system owner for the required operation when the account is too limited.
- Retry a run only when the operation is safe to repeat.
- Give the smallest required access when Check access confirms it is missing.
What to collect
Collect the tenant, workflow name and version, run ID, step name, Connection name, time, request ID, state, and visible message.
Do not collect a password, token, private key, Connection secret, request body, or customer result unless a separate secure review needs it.
Related guides
Read Build, publish, and run a workflow, Manage Connections, and Investigate a problem.
Was this page helpful?
Your answer helps us improve the documentation.
Do not include personal information, customer information, passwords, or keys.