It would be really useful to have this option available in a future version, so that if a trigger (for instance remote file trigger) is de-activated due to network/server issue, you could right-click on the job to re-activate.

I was thinking about a trigger for a trigger change and a task to enable/disable triggers.
Than the whole process can be automaticly.

I have the same issue with lots of file modifications at one which will disable the trigger due to too much file modifications.

Now I'm thinking about creating a .NET application enabling the trigger again.

Regards
Erik

---