Sending a finished scheduled report to Feishu and routing a Feishu reply back to that exact run are different things. Buda can deliver a scheduled task's result to a configured channel. But with a new Session for each run, missing information blocks that new Session; replying to the bot in Feishu normally goes to the Session attached to the Feishu conversation, not necessarily the scheduled run. To continue reliably, open that run from scheduled-task history, add the missing file, and reply in its Session. Ask the Agent to report “incomplete, missing file” rather than sending a partial report as final.
If you want the interaction to stay in Feishu, consider a scheduled task that reuses a Session pinned to that Feishu conversation. Test a missing-file case end to end to confirm the request arrives, your reply returns to the same Session, and the report resumes. When the pinned Session is waiting for input, the next automatic tick is skipped; it is not a fresh independent run. Until you verify that path, do not rely on an ordinary Feishu reply for a critical report.
We have recorded a clear “needs input → Feishu prompt → resume the exact scheduled Session” workflow as a product request. Will the report go to a private chat or a team group? The Chinese discussion covers the same distinction.