You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it make sense to have the "pause_on_error" feature as a general "try / catch" in the Workflow class?
Intended Purpose: If the feature was activated by setting the "pause_on_error" parameter for the action class, all (?) errors that are caught inside "execute_action" will be transformed to pause/retry.
Reason: Especially when working with external resources via connectors it is very cumbersome to protect any call with an extra eval. Adding eval on the top level of a method will also cause extra overhead and code.
The text was updated successfully, but these errors were encountered:
Would it make sense to have the "pause_on_error" feature as a general "try / catch" in the Workflow class?
Intended Purpose: If the feature was activated by setting the "pause_on_error" parameter for the action class, all (?) errors that are caught inside "execute_action" will be transformed to pause/retry.
Reason: Especially when working with external resources via connectors it is very cumbersome to protect any call with an extra eval. Adding eval on the top level of a method will also cause extra overhead and code.
The text was updated successfully, but these errors were encountered: