Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Make scenario stopped with errors

Short answer

When a Make scenario run fails, Make can save it as an incomplete execution and pause the scenario, or stop and roll back, depending on the setting. Scenarios that start with an instant trigger deactivate on the first error. Read the failed run, fix the cause, then resolve the stored executions.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The scenario is switched off and I did not do it.
  • Make shows incomplete executions waiting.
  • New orders or leads stopped flowing after one error.
  • The same module fails again every run.
  • I do not know which data was lost.

Why does this happen?

  1. Failed runs are stored when the setting is on

    Make saves a failed run as an incomplete execution so the data is not lost. When storing is enabled, the scenario is paused and the run goes to the incomplete executions folder. When it is disabled, the run stops and starts a rollback phase.

  2. In-order processing waits for incomplete runs

    If data is processed in the order it is received, new runs are paused until all incomplete executions are resolved. One stuck run can hold everything behind it.

  3. Instant-trigger scenarios deactivate fast

    Make states that scenarios starting with an instant trigger are deactivated immediately after the first error. You can set how many errors in a row Make accepts before deactivating a scenario.

  4. The app on the other side changed

    A revoked connection, a deleted field or a changed account makes the same module fail on each run, so the scenario never recovers on its own.

What can I do about it today?

  1. Open the failed run and read the errorNote the module name, the message and the time.
  2. Open the incomplete executionsCount them and check which data they hold before resolving any.
  3. Do not discard stored executionsThey hold the data of the runs that failed. Discarding them deletes what was not delivered.
  4. Check the connection in the failing moduleReconnect it if marked expired or revoked.
  5. Switch the scenario on only when the cause is fixedOtherwise it fails again and pauses again.

When should I bring someone in?

  • The stored executions contain orders, payments or customer messages.
  • The error returns after a reconnect.
  • You cannot tell whether partial changes were made.

How do I handle it?

  1. Reconstruct the failureI read the error, the input of the failing module and what the other app received.
  2. Fix the real causeConnections, field mapping or limits are corrected at the source.
  3. Resolve the backlog in orderStored executions are checked against the destination and rerun only where data is missing, so nothing is duplicated.
  4. Set sensible error handlingSettings for storing incomplete runs, error counts and notification are chosen on purpose, with an alert to a named person.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is my data lost when a scenario stops?

Make states that failed runs can be saved as incomplete executions so the data is not lost, if that setting is enabled.

Why did it deactivate on the first error?

Make says scenarios that start with an instant trigger are deactivated on the first error.

Can I rerun the incomplete executions?

Yes, once the cause is fixed. Check the destination first so records are not created twice.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.