Troubleshooting

Troubleshooting

Find solutions to common issues.

Troubleshooting Loopfour usually starts by separating setup problems from execution problems. Setup issues involve authentication, missing connections, expired tokens, provider permissions, or invalid workflow configuration. Execution issues happen after a workflow starts: a step may receive unexpected input, a provider may reject a request, a condition may route down the wrong branch, or an approval may remain pending longer than expected. The guides in this section help you narrow the failure before changing workflow logic.

When a run fails, collect the run ID, workflow ID, trigger payload, failed step name, provider response, and any recent connection changes. That information is usually enough to decide whether the problem belongs in the workflow definition, the integration credential, the external system, or the input data. Avoid retrying blindly in finance workflows. A retry can create duplicate invoices, messages, or records if the failed step was not idempotent. Inspect the run history first, then retry only after you understand where the previous attempt stopped.

For recurring issues, compare several failed runs instead of treating each failure as isolated. If the same provider response appears every time, start with connection permissions or request shape. If failures occur only for certain customers, invoices, or contracts, inspect the input data and mapping rules. If the workflow succeeds after manual replay, look for timing assumptions in the trigger or upstream system. This pattern keeps debugging grounded in evidence rather than guesses.