As to your specific problems:
1) I'm surprised this ever worked - but then I always used hand-code up until the 6.x release, which is when I started to play with Sequencer jobs. You are going to need to encapsulate this code into a routine, passing out your row count. Then your custom trigger can use something like:
Code: Select all
RoutineStageName.$ReturnValue > 0
2) Hmmm... if I'm following this, you have a job that runs through all jobs in a project and resets them. I did something like this a few years ago and did have issues when it tried to attach to itself - because it is currently running. Not sure why it hangs, perhaps an issue with your error handling, but you have the answer - skip over itself.
3) The Invocation ID becomes part of the job name and old versions allowed invalid characters to be used there. Now, things like commas or quoted strings can no longer be used. Unfortunately, something you'll need to work around or adapt to.
Perhaps others will post specific examples of things they used to do in earlier versions that no longer work. Fortunately, I haven't had any issues like this.