ForgeFlow Documentation

Troubleshooting

Common workflow issues and the conditions that should trigger human support.

Document ID: FORGE-TROUBLESHOOTING

Workflow failed

Open the workflow run history and identify the first failed step. Review the input and error message before retrying.

Integration disconnected

Re-authenticate the integration and run a test. If authentication repeatedly fails, create a support ticket with the integration name and error message.

Workflow is delayed

Check whether the workflow is waiting on an external service, rate limit, scheduled trigger, or manual approval.

Data is missing

Verify the trigger payload and the mapping used by downstream steps. Do not assume a missing value is correct.

When to escalate

Repeated failures, suspected duplicate charges, security concerns, data loss, account-access problems, or requests outside documented policy should be routed to a human.

AI support rule: The future support agent should answer from this documentation when relevant. If the required information is not present, it should not invent an answer and should offer human escalation.