Logs and monitoring

#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

1. Open the failed run and read the error message — FileAgent surfaces the underlying connection, permission, or path error.
2. Test the job's credential (Credentials → Test connection).
3. Confirm the source and destination paths still exist and the account still has access.
4. 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: 7 days on Free, 90 days on Pro, 365 days on Business, and agreed retention on Enterprise. Runs older than your window are pruned by scheduled maintenance; retention covers run records and their per-file detail, backup run records, and the daily application logs that hold activity events. It never deletes transferred files, archived files, or Scheduled Purge targets. If a plan change shortens retention, existing history is kept until an administrator confirms the shorter period in System Configuration. 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.