When a run fails, its page tells you which step failed, what that step received, and the error the service or Bizomate gave. This article takes you from the failure notice to a run that works.

Who can do this

Everyone in the workspace can read a failed run. Changing the workflow and selecting Run again is for workspace Admins and Editors.

Steps

  1. Open the failed run:
    • from the notification Weekly sales summary failed, select View run; or
    • select Runs in the bar at the top of the page, select Failed only, and open the run.
  2. Read the red banner under the facts row: Step 3, Create invoice, failed., whether the steps before it completed, and the error.
  3. Select Jump to the failure. The failed step opens.
  4. Compare its Input with what you expected. Most failures are a value from an earlier step that was empty or in the wrong form.
  5. Select Open the workflow at the top right. The designer opens.
  6. Fix the cause — see the table below — and publish the workflow if you changed it.
  7. Go back to the failed run and select Run again. See Run a workflow again from a past run.

What happens next

When the next run of the workflow succeeds, the Admins and Editors of the workspace get a notification that it is running again, and the failure notification is marked as dealt with.

Good to know

  • Who is told about a failure: every Admin and Editor of the workspace, through a notification with View run. Test runs never notify anyone.
  • What a failed step did before it failed stands. Steps that completed before it are not undone; the banner says how many.
  • Each step decides what a failure does, under If this step fails in its settings: stop the run (the default), try again up to 5 times, or carry on and pass the error along. See Make a step try again when it fails.
  • Time limits: one step has 60 seconds (10 minutes for a step that sends or fetches files); one stretch of a live run has 15 minutes, with time spent at a Wait step not counted; a test run has 5 minutes in all, waits included.
  • A loop is limited to 10,000 steps in one stretch of a run.

If something goes wrong

These are messages Bizomate itself gives. Messages from a service — Xero, HubSpot, Microsoft and others — appear as the service gave them.

What you see Why What to do
The step took longer than 60 seconds and was stopped. The service did not answer in time. Run it again. If it keeps happening, ask for less at once — fewer rows or items per step.
Stopped after 15 minutes. A run that needs longer should wait between steps. The live run went on for more than 15 minutes without waiting. Split the work, or add a Wait step between long stretches.
This test run stopped after 5 minutes. A test run has 5 minutes in all. Test with less data, or pin data on slow steps.
More than 10,000 steps ran in one go, so the run was stopped. Look for a loop over far more items than expected. A loop ran over far more items than intended. Check what goes into the loop; filter it first.
Version 3 is no longer kept, so there was nothing to run. The version the run was meant to use was removed by the plan's version limit. Publish the workflow again and select Run again.
The workflow has no trigger. The published version has no trigger step. Add a trigger in the designer and publish.
This kind of step no longer exists. Remove it from the workflow. The workflow uses a step Bizomate no longer offers. Remove or replace the step, and publish.
A Wait cannot run inside Loop Over Items. Move it after the loop. A Wait step is inside a loop. Move the Wait after the loop.
The run could not be carried on from where it stopped. A waiting run could not pick up where it left off. Select Run again.
Something went wrong inside this step, not in your settings. We have been told. The step failed for a reason on our side. Run it again later. If it keeps happening, raise a ticket and attach the run log.
The run stopped unexpectedly several times and was given up. We have been told. The run failed three times for a reason on our side. Select Run again. If it happens again, raise a ticket.
… is too large to pass between steps — the limit is 250 MB. A file was over 250 MB. Use a smaller file, or pass a link.
Item 3 of 12: … before the error The step ran once per item, and item 3 failed. Open the step's Input to see that item.