Why does my scheduled Flow fail with a Dropbox connection error?
Every Dropbox Flow action runs as the user executing the Flow, using that user's own Dropbox connection. In a scheduled or automated Flow, that is the automation user, and if that user has never connected a Dropbox account, every Dropbox action will fail, even though the Flow runs in system context.
To fix it, log in as the user the automation runs as and connect Dropbox from the File Manager. That user also needs the Dropbox Standard or Dropbox Admin permission set, and the org's workspace setup must be complete so a Dropbox root folder exists.
To fail gracefully, start the Flow with the Check Dropbox Connection action and branch on its isConnected output, for example creating a task for an administrator instead of letting the Flow error.
Note: Check Dropbox Connection has no success output, unlike the other Dropbox actions. Branch on isConnected.
