Agent running across day/night boundary; how Amgr determines timeout

I’m writting an agent that might potentially execute for very long, but also can be stopped resumed.

So I’d like to add a code that stops it gracefully before the amgr shoots it down. I can read the server document and determine the current timeout values (or use defaults) and track the time used.

What I wonder about is – if the agent has been started in nighttime (with say 20 min limit) then continues in daytime (with 10 min limit). The question is – will amgr use nighttime or daytime limit to shoot it down? I could of course test this myself, but maybe somebody knows the answer already :slight_smile:

Cheers

Normunds