Deployment troubleshooting
Common problems with scheduled, triggered, service, and data app deployments, and their fixes.
Deployment can't access a file that the workflow reads or writes
Cause: Under team scope, the deployment runs with the team's permissions, not with any individual user's. A workflow that reads or writes a file using a path tied to a specific user's personal space or file access fails, because the team doesn't inherit that user's personal access. See Deployment execution scope.
Fix:
- Open the deployment's Edit dialog and check Execution Scope under Advanced configuration > Additional settings.
- If the workflow needs the executing user's own file access, recreate the deployment with user scope.
- If the deployment must stay on team scope — for example, a shared scheduled job — move the files it reads or writes into a space the team has access to, or replace the personal authentication with a team-scoped secret.
Manual run shows "Finished successfully" instead of the data app
Cause: The workflow was saved in an executed state. A run starts from the saved state, so when every node is already executed, there's nothing left to run and the data app pages never open.
Fix:
- Open the workflow in the workflow editor.
- Select all nodes and reset them.
- Start a new manual run.
If the data app is deployed, also create a new version and update the deployment to use it. Deployments run from a pinned version, so resetting the working copy doesn't affect them.