I did learn something, though. Completely logical, I just hadn't run across it before now.
If the server's agent manager is overloaded, those 5 minute / 30 minute response times aren't real.
We had a couple of scheduled agents jump in on the server at the same time, and they both exhausted the 30 minute limit on their runs.
We only had 2 agent manager work threads.
Well, the triggered agent was delayed by 30 minutes.
The good news was that it was not ignored. The triggered agent fired just like it should, it was simply delayed in execution.
So the trigger isn't ignored, even when there's no work thread available to handle it.
What causes a triggered agent to st... (Mike Woolsey 1.May.18)
Feedback response number WEBBAYKTK9 created by Mike Woolsey on 05/08/2018
. . Some Ideas (Barry Shapiro 2.May.18)
. . . . Nothing on the log. (Mike Woolsey 3.May.18)
. . . . Another interesting thought that tu... (Mike Woolsey 8.May.18)
. . Speculation - corrupt agent documen... (Scott Leis 6.May.18)
. . . . I ran across an agent on a differen... (Mike Woolsey 8.May.18)