Fortra’s GoAnywhere MFT now includes an AI‑driven Guided Diagnostics capability that automatically analyses failed file transfers and suggests remediation steps. The vendor estimates that the feature can reclaim as much as 160 hours of administrator effort annually – roughly 3 hours per week – by reducing the time spent hunting for root causes.
How Guided Diagnostics works
The feature runs inside the GoAnywhere runtime and consumes the transfer logs that already exist for each job. When a job fails, the AI model classifies the error into one of four categories that the vendor observes most frequently: authentication, network, permissions, or missing file. It then correlates the log entries with known patterns and presents a concise diagnostic view to the operator.
In a recent demonstration, a simulated failure that took 50 minutes to resolve was broken down as follows:
- Investigation time: ~40 minutes (log search, partner communication) - Fix time: 5‑10 minutes (key update, connection test)
The underlying cause was an authentication error caused by a partner rotating its SSH keys without notification, leaving GoAnywhere to attempt a connection with an obsolete key.
Operational impact for DevOps and SRE teams
From an operations perspective, the AI layer shifts the troubleshooting workflow from manual log mining to a guided, repeatable process. Practitioners can expect:
- Reduced mean time to resolution (MTTR) for transfer‑related incidents.
- More predictable on‑call load because routine failures are triaged automatically.
- Potential integration points with existing observability stacks – the diagnostic output can be forwarded to alerting pipelines or ticketing systems.
Because the feature is embedded in GoAnywhere, teams do not need to provision separate AI services, but they should account for the additional compute footprint required to run the model alongside the MFT engine.
Security considerations
The diagnostic process surfaces credential‑related failures, such as expired or rotated SSH keys, earlier in the incident lifecycle. This can improve the security posture of the file‑transfer ecosystem by prompting faster key rotation and verification. However, operators should be aware that the AI model ingests log data that may contain sensitive identifiers. Organizations must verify that the model’s execution environment complies with their data‑handling policies and that log retention settings do not expose credentials beyond what is required for diagnostics.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Teams responsible for managed file transfer should evaluate the accuracy of Guided Diagnostics against their own failure patterns and measure the actual time saved in their environment. Consider piloting the feature on a subset of critical jobs, integrating the diagnostic output with existing monitoring tools, and reviewing any data‑privacy implications of feeding logs to the AI engine. If the model proves reliable, it can become a standard part of the incident‑response playbook, freeing engineers to focus on higher‑value work while maintaining a tighter security loop around credential changes.