I have a “When documents have been created or modified” agent that has been working perfectly. It would kick off maybe 10 minutes after a document was modified.
Now the agent never seems to kick off or at least not when expected. I created a new document in the database around 5 PM yesterday. The agent did not run till 12:16 AM the next morning.
I am not sure if the execution of this agent was due to my document creation or not. But seven hours later?
Is there some kind of setting on the server that determines when this type of agent will kick off? What else would prevent this agent from running?
The agent is enabled.
It is set to run on the same server that the database is on.
Subject: Have documents been created or modified not running when it should
Bruce,
It almost sounds like the agent queues itself and hangs until the agent refreshes its cache–(ours is set for midnight, and I think that is how it is set out of the box, so if your admins didn’t change it, it would be the same.) Then, once the cache is refreshed, it kicks off the agent.
I couldn’t find anything in the IBM KB about the trigger “When documents have been created or modified” but I did find a technote about “new mail triggered” agents…and from some of Julie Kadashevich’s agent articles, I am lead to believe the two triggers are much the same.
Subject: RE: Have documents been created or modified not running when it should
I’m thinking it might be the agent itself. Something in the code (which I find hard to beleieve that code could cause agent from kicking off but it’s Notes).