Break Error Handler not creating Incomplete Executions (Status Success instead of Warning)

Beginner Questions
1

:bullseye: What is your goal?

I want to use the Break error handler to manage temporary API errors. My goal is to have the scenario automatically retry the execution after 10 minutes when an error occurs, instead of failing or finishing without retrying.

:thinking: What is the problem?

When an error occurs, the scenario finishes with a Success status instead of Warning. No record is created in the Incomplete Executions tab, and the scheduled retry after 10 minutes never happens. I am on the Free Plan, and I’m trying to figure out if this is a plan limitation or a configuration error.

:test_tube: What have you tried so far?

Added the Break error handler to the module.
Set the retry interval to 10 minutes and attempts to 3.
Checked the Scenario Settings, but the execution still completes as “Success”.
Verified that I haven’t reached my total storage limits for the account.

:camera_with_flash: Screenshots: scenario setup, module configuration, errors

2026-04-18_09-56-20.png
2026-04-18_09-56-20.png1798×820 126 KB

3

Hey there,

There is no error happening in the screenshot you shared. The module is timing out. You will need different logic here. Maybe check with a router and filters and retry the call manually if a timeout happens.

4

This is a known behavior that catches people off guard — it usually comes down to one of two things.

1. Incomplete Executions must be explicitly enabled

Go to Scenario Settings and turn on Allow storing incomplete executions". Without this toggle, the `Break` directive silently marks the execution as successful, because there is nowhere to store the incomplete state. It is not enabled by default.

2. The Break handler must be attached directly to the failing module

If your error route has additional modules between the failing module and the `Break` directive, and one of those intermediate modules also errors, the chain can complete without triggering Break correctly.

To verify the setup:

- Attach the error handler route directly from the failing module

- Place the `Break` module as the first and only module in that route

- Configure retry attempts and interval directly inside the Break module settings - they are in the same module, not a separate configuration

I built a tested blueprint for exactly this pattern - happy to share.