Why does this bank statement import error occur some days and some days not? The imports are scheduled only once a day, but sometimes I see this on the same day as a successful import. Error message: Import-level FailureThere was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded.

AI generated answer (using internal Slack threads):

The error message you're seeing, "Import-level FailureThere was a problem connecting to your financial institution. The file matching the configuration record has already been uploaded," suggests that the same file is being uploaded more than once. This could be due to a few reasons: 1. Duplicate Uploads: The same file might be getting uploaded more than once. This could be due to a manual error or an issue with the scheduled script that is supposed to upload the file. 2. Incorrect File Handling: After a successful import, the file should ideally be moved to a different location or renamed to prevent re-upload. If this is not happening, it could lead to the same file being uploaded again. 3. Timing Issues: If the import is scheduled close to the time when the bank statement is generated, there could be instances where the statement is not ready at the time of import, leading to the import of the previous day's file. To resolve this issue, you should review your file handling and upload processes. Ensure that files are correctly moved or renamed after a successful import to prevent re-upload. Also, consider adjusting the timing of the scheduled import to ensure that the bank statement is ready at the time of import. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******