Pros / Cons on scheduling scripts every 30 minutes based on a saved search to process the resulting records? Verses a UE script that triggers the scheduled or M/R event based manually.

Major con of the UE trigger the SCH is you might need to manage multiple deployments. A single deployment cannot be running simultaneously, so if the SCH is running and UE tries to fire again it will error unless you create another deployment of SCH or tell it not to.

I have that covered already. I can create a new deployment on the fly if one isn't available.

How long does the result processing take? The more simultaneous Deployments you have, the more you'll be backing up queues or spreading across them. Either way, you might be blocking up threads for other potentially more critical processes.

@dcrsmith can we have a bit more context/usage? these hybrid scenarios sounds to me something that should consider UE+N/cache Personally, I would weigh the trigger point a lot heavier, and try to analyse if it is possible to reduce units via the trigger-point, if possible via cache or doing some mapping to create an object that contains everthing than have scheduling scripts that can break if in your first case, the run time exceeds the scheduling, creating repeated jobs, or a UE that triggers schdeuled which may also create repeated jobs (but additional benefits to the second one because at least the browser wont be in a terribly long loop, dependent on design)