GitHub Repo
Dify Community Proposes Schedule Identity Fix for Agent Files That Upload but Cannot Be Retrieved
A Dify community report on October 26 said scheduled workflows may misidentify workspace accounts as end users, preventing retrieval of files generated by Agents. Two fix proposals have been submitted, but neither had been merged as of the latest check; deployment environment validation is still pending.
On October 26, the Dify community reported that workflows containing the newer Agent node could generate files when run manually in Studio, but failed with ToolFile not found when triggered by a schedule. The reporter used a self-hosted Kubernetes environment and observed that the file upload succeeded, but the subsequent download request failed. Although the Agent node was marked successful, a downstream step stopped because the files variable was missing. Issue report
This type of failure can directly affect automated report delivery. Dify’s official documentation describes Schedule Trigger as an entry point for running workflows on a schedule, with recurring intervals configurable through the visual interface or cron. It lists daily reports and notifications as use cases. In this context, passing a manual test in the editor alone does not demonstrate that a background schedule can deliver files successfully. Official scheduling documentation
The proposed fixes point to an inconsistency between the call source and how the user’s identity is derived: the schedule runs with the SERVICE_API source, but the actual initiator is a workspace Account. The runner nevertheless labels it as an end-user based on the source. During upload, the file is associated with the mapped end user; during download, the system looks it up using the original account ID. As a result, the two sides cannot find the same record. PR #44799 proposes recording the role at the entry point, while the actual user object is still available, so the runner can prioritize using it. Identity propagation fix
A second proposal, PR #44796, also covers pause snapshots and resumed executions, while remaining compatible with older snapshots that do not record a role. The author said 103 related tests passed, covering file creation, download reconstruction, and denial of access to other users and tenants. However, the author did not test external Agent services or deployed scheduled workflows beyond local testing. Both proposals remained open as of the latest check, so the issue cannot be considered fixed in an official release. Engineering teams should track merge and release status, then verify actual scheduled runs, including first execution, pause and resume, and consistent file permissions. Fixes and validation scope