Error handling and alerts
How FileAgent handles failures — automatic retries, clear errors, and notifications — and what to check first when a job fails.
Last updated July 17, 2026
#What happens when a transfer fails
When a run fails, FileAgent marks it failed and records the full error in Logs. If retries are configured, transient errors are reattempted automatically before the run is marked failed. If alerts are set up, you're notified by email (or Slack/Teams on higher plans).
#What to check first
- Open the failed run and read the error message.
- Is the scheduler running? (System Status / Dashboard.)
- Does the credential still test successfully?
- Do the source and destination paths still exist, with the right access?
- Run now after a fix to confirm before the next schedule.
#Make failures find you
Add failure alerts to every production job. The goal is that a problem reaches you before a stakeholder does. Add “no files” alerts where silence would be a problem, and reserve success alerts for the few jobs someone is actively waiting on.
Configure channels and triggers under Notifications.
#Going deeper
For specific symptoms — connection errors, scheduling problems, certificate warnings, license issues — start at Troubleshooting.