v4.0.1

1. Fixed an issue that produced an incorrect error message when invoking retry.actions and retry.action from Developer tools → Actions.
2. An exception is now raised when a retry loop is canceled due to a duplicate retry_id, ensuring that subsequent steps do not continue when used inside automations or scripts.

Full Changelog: v4.0.0...v4.0.1

4.0.0

Breaking Change: retry.action now executes its retry loop(s) synchronously (blocking) instead of running in the background. This enables:

• Proper error propagation: The exception from the final retry attempt is now raised. When used inside automations or scripts, this will halt execution of subsequent steps unless continuing-on-error is enabled.
• Returning response data on success.

No configuration changes are required.
However, if you previously implemented workarounds to compensate for the old non-blocking behavior, you can safely remove them now.