n8n Dropbox Upload Fails with 17 MB Files Due to Connection Loss

Below is some guidance based on the Dropbox integration and general n8n behavior:

File Size Limit for Dropbox Uploads in n8n

There isn’t a specific file size limit imposed by the Dropbox credentials or node in n8n. Any limits typically come from Dropbox’s API itself or from the way larger file uploads are handled (for example, via chunked uploads in some cases). At 17 MB, you’re well below common size limits enforced by Dropbox.

Possible Causes for the "Connection Lost" Error

The error message “Connection Lost (You have a connection issue or the server is down. n8n should reconnect automatically once the issue is resolved.)” is generic and can be triggered by several factors:

• Network Interruptions: Temporary network instability between your n8n Cloud instance and Dropbox’s servers can cause connections to drop.
• Timeouts during Transfer: Uploading binary data (even medium-sized files in memory) can sometimes trigger timeouts if there are delays in data transfer.
• Cloud Instance Limitations: Although less likely with a 17 MB file, performance constraints (like memory or CPU spikes during execution) on your n8n Cloud instance could contribute. Keep in mind that binary data processing can be resource intensive.
• Intermittent Connectivity: General internet issues (or in-between services) may also be at play.

Recommendations

• Double-check Network Stability: Ensure that your internet connection and any network configurations (like proxies or firewalls) aren’t interrupting the upload process.
• Monitor n8n Instance Resources: While the file size seems small, reviewing the logs or monitoring your instance’s health might reveal if resource limits or timeouts are being reached.
• Test at Different Times: Intermittent behavior can sometimes be isolated by testing uploads at different times to determine if the issue is load-related.
• Review Dropbox API Status: Although less common, check if Dropbox is experiencing issues that could lead to dropped connections.

If issues continue after these checks, it may help to examine detailed logs from the n8n Cloud instance, or consider splitting the file into smaller chunks using a workflow strategy if you suspect timeouts are directly related to upload time.

Let me know if you need further specifics on configuring or troubleshooting your workflow!