Intermittent Dropbox 'New File' error: sharing/create_shared_link fails on first run but succeeds on re-exe

Your Workflow URL
https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZkMDYzNTA0Mzc1MjZmNTUzMzUxM2Ii_pc
Your Task History ID
IjU3NjUwNTY1MDYzNTA0MzA1MjY5NTUzYzUxMzY1MTYwNTQzOTBmMzEi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
Hello Pabbly Connect Support Team,

I’m experiencing an intermittent issue with the Dropbox trigger “New File” in Pabbly Connect.

Problem summary
When a new file appears in a specific Dropbox folder, the workflow sometimes fails on the first execution while trying to generate a shareable link. If I go to Task History and click Re-execute, it then runs successfully.

Error shown (Task History → Data Out → Res2 Response)
“Error in call to API function ‘sharing/create_shared_link’: Inval…”

Example task details

  • App/Trigger: Dropbox — New File
  • Workflow: 1.1.2 Estudos Youtube (name shown in Task History)
  • Timestamp: Dec 27, 2025 21:55:12
  • File name: Ethereum__Dubious Speculation.mp3
  • File path (lower): /estudos/ethereum__dubious speculation.mp3
  • File path (display): /Estudos/Ethereum__Dubious Speculation.mp3
Expected behavior
The workflow should complete successfully on the first run and return the shareable link.

Actual behavior
The first run shows the error above (sometimes the step still appears as “Success”, but the response contains the error). Re-executing immediately after works.

My suspicion
This looks like a timing/race condition (e.g., the file triggers the workflow before Dropbox fully finalizes the file or allows sharing). A short delay or an automatic retry on the sharing/create_shared_link call might resolve it.

Could you please investigate and advise:

  1. if this is a known issue in the Dropbox integration, and
  2. if there’s a recommended workaround (delay step, retry setting, different action, etc.)?
I can provide additional logs or a screen recording if needed. I’ve attached a screenshot showing the exact response in Task History.

Thanks,
Bruno
 
Top