Logs and monitoring
Every run is recorded with status, duration, file counts, sizes, and per-file detail. Find run history, read the signals, and investigate failures.
Last updated July 17, 2026
#Where to view run history
The Logs page lists every job run — newest first — with job name, status, start time, duration, file count, and transfer size. Click any run for its full detail, including the list of files transferred and the complete error text for failures. Filter by job, status, or date to narrow the view.
#Signals worth watching
- Duration creeping up → a growing data set or a slowing endpoint; consider narrowing the job's scope or splitting it.
- File count suddenly zero → an upstream producer may have stopped delivering; a success with 0 files can still be a business problem.
- Size spikes → an early warning before storage or bandwidth becomes an issue.
- Recurring partial-success runs → usually a setting (often conflict handling) that needs adjusting.
#Investigating a failed run
- Open the failed run and read the error message — FileAgent surfaces the underlying connection, permission, or path error.
- Test the job's credential (Credentials → Test connection).
- Confirm the source and destination paths still exist and the account still has access.
- Fix the cause, then Run now to confirm before the next schedule.
Common failure patterns and fixes are in Troubleshooting.
#Retention
Run history is kept according to your plan — from short windows on entry plans up to a year on Business Premium, with custom retention on Enterprise. Runs older than your window are pruned. If a run seems “missing,” check the date filter and your retention window; a failed run would still produce an entry, while no entry at all usually means the job never started.