Download the tool via this link (Note: You must be logged in for the download to work correctly).
The Trigger: The Orchestrator runs on a 30-minute Scheduler. It acts as a watchman, scanning for any unsent exceptions. If it finds new ones, it dispatches them to the configured email immediately. Need a faster response? You can easily tighten the schedule to run every 5 minutes.
The Brain (P952000): Set up the Cross-Reference (e.g., "ORCH_ItemUpdate") to tell the system what to look for.
The Flow: The Orchestrator checks the cross-reference and scans the exception logs for any unreported occurrences. If it spots a match, it alerts the configured email address.
The Secret Sauce: This works beautifully even for "naked" orchestrations (those without defensive code). Why? Because you are triggering this logic after the system records the failure, not inside the workflow that just crashed.
So, if you're running "naked" orchestrations because error handling felt like too much work, you are officially out of excuses. No more flying blind. Download it, plug it in, and stop letting errors slip through the cracks.
Mario Garcia
