Skip to main content
Question

FTP Caller Fail "Number of redirects hit maximum amount"

  • November 19, 2025
  • 2 replies
  • 28 views
fionasin
Contributor
Forum|alt.badge.img+10

I have a job that downloads 7 text files from an FTP directory, and for the last 3 days, 6/7 files have downloaded but 1 always fails (the same one each time) with the error: Number of redirects hit maximum amount

I am aware of the post below, but as no similar setting exists on the FTP caller, I’m lost. 

I can upload fine, and manually downloading the files by logging into the FTP site, or using a WinSCP script also works. The file that failed today was empty (0MB), but so are some of the other files it downloads, and yesterdays file had records and still failed. Empty files are not uncommon for this job, and it has never presented an issue before. 

This has started occurring since upgrading to 2025.1.3 from 2022, and occurs on both FME Flow and Form. This error has so far not appeared in any other workspaces that use FTP callers, even for multiple file downloads at once. I’m leaning toward this being an issue with the file, rather than the FTP, but I cannot see a problem with the file that would cause this. It is simply a txt file. 

Edit 20/11/25: This issue is now affecting multiple workspaces with FTP callers

 

FME Flow 2025.1.3
Build 25643 - win64

FME(R) 2025.1.3.0 (20251001 - Build 25643 - WIN64)

2 replies

donalmateer
Safer
Forum|alt.badge.img+7
  • donalmateerSafer
  • Safer
  • November 20, 2025

Hey ​@fionasin 
I'd like to understand this a bit further to try get to the root of the issue.

To confirm this issue has only appeared once you've updated? Does the same workspace still work in previous versions? Would you be able to test?
Does the file (that is being rejected) have a specific filename? 

As you mentioned it seems specific towards 2025. Perhaps it could be a proxy issue.
For a possible test run - go to Network Proxy in FME Options and if you have the options set as 'Use system proxy settings' change to 'No Proxy'. Test run your file to see if it successful 
If it still fails, I would ask you to enable detailed logging to capture the FTP transaction for the failing file. If you could share that log file it could help us troubleshoot further.

fionasin
Contributor
Forum|alt.badge.img+10
  • fionasinContributor
  • Author
  • Contributor
  • November 21, 2025

Hey ​@fionasin 
I'd like to understand this a bit further to try get to the root of the issue.

To confirm this issue has only appeared once you've updated? Does the same workspace still work in previous versions? Would you be able to test?
Does the file (that is being rejected) have a specific filename? 

As you mentioned it seems specific towards 2025. Perhaps it could be a proxy issue.
For a possible test run - go to Network Proxy in FME Options and if you have the options set as 'Use system proxy settings' change to 'No Proxy'. Test run your file to see if it successful 
If it still fails, I would ask you to enable detailed logging to capture the FTP transaction for the failing file. If you could share that log file it could help us troubleshoot further.

Hi ​@donalmateer 

The file being picked up does have a specific file name, but as I mentioned in the update, this does impact multiple process’ now. I can tell you that there is no change in behaviour when switching to ‘No Proxy’. 

Unfortunately, I cannot share my logfile with you as it contains passwords and sites I need to keep protected, but below is an excerpt (with the host name redacted, but it is just an IP)

2025-11-21 11:53:47|   0.3|  0.0|INFORM|        FTPCaller_5 (FTPFactory): FTP info: Re-using existing connection with host ****
2025-11-21 11:53:47|   0.4|  0.1|INFORM|        FTPCaller_5 (FTPFactory): FTP info: abort upload
2025-11-21 11:53:47|   0.4|  0.0|INFORM|        FTPCaller_5 (FTPFactory): FTP info: Connection died, retrying a fresh connect (retry count: 1)
2025-11-21 11:53:47|   0.4|  0.0|INFORM|        FTPCaller_5 (FTPFactory): FTP info: shutting down connection #0
2025-11-21 11:53:47|   0.4|  0.0|ERROR |416454  FTPCaller_5 (FTPFactory): FTP/FTPS/SFTP transfer error: Number of redirects hit maximum amount
2025-11-21 11:53:47|   0.4|  0.0|INFORM|        FTPCaller_5 (FTPFactory): FTP info: Hostname **** was found in DNS cache

I’m not sure if I have an answer to why this is happening, but I think I do have a solution. The issue with the original workspace seems to have magically resolved on its own, but it pops up in other workbenches. I think what these workbenches have in common is that there are multiple transformers feeding into a single FTP caller, using an attribute value for the file name. This results in 1 or 2 files getting the aforementioned error. However, if I split the FTP callers out into separate streams, everything downloads successfully. 

Community Stats

32,126
Posts
121,959
Replies
39,776
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.