Azure Logic App FTP连接器无法触发修改日期早于当前日期的文件

I've run into this exact issue before with the Azure Logic Apps FTP trigger—here's how you can get it to trigger for any new files, regardless of their modified date:

Why this happens #

By default, the FTP trigger uses a start time as a reference point. It only considers files with modified dates after this start time as "new" and worth triggering on. If you're uploading files with modified dates older than the trigger's configured start time, it'll mark them as already processed and return a 202 status (which just means "I got your request, but there's nothing new to process").

Step-by-step fixes #

1. Adjust the trigger's Start Time #

• Open your Logic App and navigate to the FTP trigger configuration.
• Look for the Start time setting (it might be under "Advanced options" depending on your trigger version).
• Set this time to a date way earlier than the oldest file you need to process (e.g., a year ago, or even the start of 2000 if you're unsure). This tells the trigger to treat all files modified after this point as eligible for triggering, no matter when you upload them.
• Save your changes and let the trigger re-scan the directory.

2. Check the File Detection Mode #

• Some versions of the FTP trigger include a Detection mode option. If yours does:
  • Switch it from the default (usually "Detect only new files") to "Detect all files (including existing ones)".
  • This ensures that any file added to the monitored directory—even if it has an old modified date—will trigger the workflow.
• Also, double-check that the Recurse option is enabled if you need to monitor subdirectories.

3. Reset the trigger's scan state #

If adjusting settings doesn't work, the trigger might have cached a scan state that's ignoring old files. Try these steps:

• Pause and restart your Logic App: This resets the trigger's internal tracking of processed files.
• Temporarily change the monitored directory: Switch the trigger to watch a different folder, save the change, then switch it back to your original directory. This forces the trigger to re-scan the original folder from scratch, picking up all files regardless of their modified date.

4. Remove unintended filters #

• Head to the trigger's Advanced options and make sure there are no filters set that restrict modified dates (e.g., a filter that only includes files modified "today").
• Also, check for filename filters that might be excluding the files you're trying to process.

Note on the 202 status code #

That 202 "Accepted" status is normal in this scenario—it just means the trigger ran, scanned the directory, and didn't find any files that matched its default eligibility criteria. Once you adjust the settings above, you'll stop seeing these skipped runs for your older files.

内容的提问来源于stack exchange，提问作者Shubham Awasthi