Error messages explained

Read the error messages you are most likely to see on a failed run, explained in plain words, with the usual cause and what to do next.

When a run fails, open it and select the step marked Failed. Under What went wrong, Loopfour explains the cause. This page covers the messages you are most likely to see. In the messages below, the name of your system and step appears where this page shows QuickBooks or a step name.

How to read a failed step

What went wrong is the cause in plain words.
You can fix this means you, or someone on your team, can fix it. The steps follow under To fix it.
Loopfour support needs to fix this means the problem is on Loopfour's side. What happens next says whether support has already been told.
Already done in this run lists work the run finished before it failed, such as a record it created, so you do not repeat it.
Explained by Loopfour AI marks an explanation written by AI from the error. Read it as a likely cause, and check it against the step's Error tab.

Connection messages

Message	What it means	What to do
QuickBooks access expired. QuickBooks refused this block because the connection to your QuickBooks account is no longer valid.	The system no longer accepts Loopfour's access.	Select Reconnect, then retry from this step. See A connection stopped working.
Didn't start: QuickBooks isn't connected to this workflow	The workflow uses a system that is not connected. Nothing ran.	Select Connect, then retry. Nothing is repeated.
Didn't start: more than one QuickBooks account is connected and none is the default	Loopfour cannot tell which account to use. Nothing ran.	On Integrations, set a default account, then retry.

Approval messages

Message	What it means	What to do
Approval step "Approve bill" was rejected, followed by the reason	An approver rejected the request. By default the run stops here.	Read the reason. If the request should go again, retry the run; the approval is asked again.
Approval step "Approve bill" was not approved before timeout	Nobody decided in time, and the step was set to reject on timeout.	Retry the run to ask again, or change the step's Timeout.
Approval step "…" timed out after 7d	Nobody decided in time, and the step fails on timeout. This message shows the step's internal ID rather than its name.	Retry the run to ask again, or change the step's Timeout.
Escalated approval step "…" timed out, followed by the original and escalation approvers	The request was escalated and the escalation approvers did not decide in time either.	Retry the run. Tell the escalation approvers to decide in Studio under Approvals.
Approval request delivery failed: no notification reached an approver	The step tried to send email or Slack messages and none arrived. The reason follows in brackets, for example a Slack problem.	Fix the channel, such as reconnecting Slack, then retry. See An approval request did not arrive.

Messages from your systems

When a connected system refuses a request, the message usually includes that system's own reason, such as a missing customer or a field it will not accept. Fix the record or the setting in that system, then retry from the failed step. If the message names a field, compare it with the step's Input tab to see what Loopfour sent.

Messages when you approve, reject or retry

Message	What it means
Could not record your decision	Someone else decided first, the time ran out, or the run was stopped. Open the run to see its status.
This approval is assigned to someone else	You are not on the approver list, and you are not an owner or admin.
This run cannot be retried yet	The run has not ended. Wait until it finishes, fails or is stopped.
We could not tell if the retry started	Look for a new run linked to this one before you try again.

Still stuck

If the message is not here, or the fix did not work, see Get help.