Every once in a while -- a long while, this has taken years before the first emerged -- an agent triggered on "create/modify documents" has simply stopped working.
The agent itself was signed back in 2015.
The agent simply stopped working. The agent log showed the date it last ran, 4/14/2018. Numerous documents came in on multiple days after that, so I know it would never restart, it's simply "dead".
The server itself restarts Amgr overnight. So after multiple days any issue scanning the DB would've been resolved.
Test of the agent revealed no scheduling or server specification problem. The agent runs on all servers, and it's presently running with the same ID it used to have (see below).
Agent Manager settings prevent an agent from running "around the clock", too. Amgr should have run it. It didn't.
I signed the agent again, and it fired within a minute of signing, and has worked smoothly since then.
But it's troubling if I need an agent to make sure an agent ran. (Infinite regression comes to mind.)
What causes a triggered agent to st... (Mike Woolsey 1.May.18)
Feedback number WEBBAYCMVQ created by Mike Woolsey on 05/01/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)