Not sure if this changed but I can't think of anything in server 2016.
Couldn't find a resubmit job action in the current API documentation either so I think the way for now is to query the jobs for failures, query the failed jobs, resubmit the failed jobs and add the previous job id to the new job in an optional published parameter. (In a Workspace using the API, not by hand.)
Re-using id's is a great way for misery, I wouldn't vote for that kind of solution.
Not sure if this changed but I can't think of anything in server 2016.
Couldn't find a resubmit job action in the current API documentation either so I think the way for now is to query the jobs for failures, query the failed jobs, resubmit the failed jobs and add the previous job id to the new job in an optional published parameter. (In a Workspace using the API, not by hand.)
Re-using id's is a great way for misery, I wouldn't vote for that kind of solution.
I agree, I would rather not re-use an ID, but I need to have the traceability. Maybe adding another optional parameter would work for if it was resubmitted. Thanks!
Hi @colleenk_1
You're right that information to help trace resubmitted jobs would be helpful. We have a related idea over
here. Would you consider adding some comments there as to what you'd like to see? Optionally, you can always create a new idea more focused on the specific feature you envision.
Thanks for your feedback!
Nathan
Hi @colleenk_1
You're right that information to help trace resubmitted jobs would be helpful. We have a related idea over
here. Would you consider adding some comments there as to what you'd like to see? Optionally, you can always create a new idea more focused on the specific feature you envision.
Thanks for your feedback!
Nathan
Definitely! Thanks, @NathanAtSafe