You start a file listener before a scheduled run. The file listener that is triggered manually runs and stops at the start time of the schedule run.
You start a file listener after the end time of a schedule run. The file listener runs once and stops.
You cannot start a file listener manually when a file listener is already running according to the run schedule.
When the agent version is upgraded, the file listener is automatically submitted to the new agent version and the old version is stopped.
If the agent fails, such as a temporary network disruption, the file listener is automatically submitted to the agent when the agent restarts. Events such as
that were submitted when the agent failed are notified by the file listener when the agent restarts.
You stop an existing file listener run. The file listener stops listening to files for that run. A new run starts at the time of the next schedule time unless the file listener is started manually.
A file listener fails to start if the file listener is disabled, it is not associated to a task, or if the associated secure agent is down.
A file listener fails to start if the number of file events such as arrive, update, or delete, exceeds the maximum event limit (10000 files).