The only reason I considered using the action tab is because I have a script to run as the next step. So instead of creating a job definition with the new script wouldnt it be better to add the script to the post running action 'source'?
The issue I'm f acing is, if I test the script in shell it works but not when I place it in the source of the post running action.
Most of the times it is more transparent to have different actions in different steps in a job chain. Especially when you want to only restart parts of the different tasks. Also for troubleshooting, if the job goes to error, the error might be in the actual job or in the post running action. Therefore most of the times using a job definition for the script is more convenient. Also the script 'context' is a little different between a job definition and a post running action, that might be the reason your script works in the shell but not in the action.
Did you test your code out in a RedwoodScript job definition?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.