I am running an SP via "Custom command" as a "Database command" that runs some bulk imports with some complexity (format files, etc).
When it returns any error (Such as records dropped due to data truncation), what is a good way to get the job to continue after? I have a table that should be executing after this command, and the job is stopping after this SP returns the error output.
You can move the "Database command" action in question to a separate module and then call that module with the "Call another module/project" action in the "Capture errors and continue" mode. This will make the following actions in the main module to be executed in any case. You can detect SP errors by analyzing the output of the "Call another module/project" action.