Automation Answers

Why Is Make Storing Incomplete Executions?

Make stores an incomplete execution when a module fails mid-run and storing is on. Fix the cause, then retry or resolve each one so queued runs can continue.

By Automation Ace Editorial Team · Reviewed for technical accuracy by Troy Tessalone · Published · Updated

Short answer

Why Is Make Storing Incomplete Executions?

An incomplete execution is a run that stopped partway because a module failed. Make saves it so you can fix the problem and finish the run instead of losing the data. This only happens when storing incomplete executions is turned on in the scenario settings, or when a Break error handler catches the error. Open the Incomplete executions tab, read the error, fix the cause, and then retry or resolve each saved run.

Common causes

  • An app returned an error, such as an expired connection, a rate limit, or invalid data.
  • A Break error handler caught the error and saved the run for a retry.
  • Automatic retries ran out before the app recovered.
  • Sequential processing is on, so new runs wait until older incomplete executions are resolved, which makes the scenario look stuck.

Diagnostic steps

  1. Open the scenario's Incomplete executions tab and read the error on the failed module.
  2. Fix the root cause, such as reconnecting the app, correcting a mapping, or waiting out a rate limit.
  3. Retry the saved runs, or resolve them by hand if the work was done another way.
  4. Delete runs that should not be completed, so they don't block or clutter the queue.
  5. Add an error handler or alert so new failures are noticed quickly.

Example

A scenario that creates invoices stops on a 401 error after an accounting connection expires. Twelve incomplete executions pile up. Reconnecting the app and retrying them creates the twelve invoices without asking customers to resubmit anything.

Caveats

Retrying a run that already did part of its work can repeat those steps, such as sending an email twice. Make create steps safe to repeat, or resolve those runs by hand. Saved runs also use storage, so clear old ones regularly.