The error management feature for Data Readers introduced in version 14.4 is excellent, but it creates an operational challenge. Currently, every single data reader requires explicit configuration of an error handling group - there's no way to simply let execution continue with subsequent steps when an error occurs, which was the default behavior in earlier versions.
In practice, this means that a procedure containing 20 data readers would require creating 40 groups just to maintain the original sequential flow after error handling. This overhead quickly becomes unmanageable in complex procedures.
Additionally, I've noticed some inconsistent behavior: procedures migrated from previous versions seem to operate in a back-compatible mode that isn't documented or visible in the interface. Similarly, when copying data readers from legacy actions, they appear to inherit this undocumented behavior. This lack of transparency can be confusing.
My suggested solution: Add a "Get back" option to the "On error go to group" dropdown, functioning exactly like the return mechanism in call procedures. When selected, after executing the error handling group, the flow would automatically resume at the next step following the data reader that encountered the error.
This would eliminate the need for workaround groups while preserving full control for users who need custom error routing. For backward compatibility, migrated procedures could default to this "Get back" behavior automatically.
