[WSHAPER]

Summary

Any app declaring an optional File or ListOfFiles input breaks scheduling for every caller that omits the slot: the Assistant form omits unfilled optional fields, so this is the common path. The server resolves the missing key to null and feeds it to file resolution as an id. prepareTask then crashes with a TypeError and the schedule request fails with HTTP 500.

Changes

prepareTask now skips an optional file input slot that resolves to null instead of collecting it as a file id, so a task whose optional File/ListOfFiles slot is omitted schedules normally. Slots that are provided are validated as before.

Steps to reproduce (before this change)

1. Schedule a task type that declares an optional File or ListOfFiles input slot.
2. Omit the optional slot.
3. The schedule request fails with HTTP 500: the missing key resolves to null and is passed to getFirstNodeById as a file id, which only accepts int.

With this change the same request returns a scheduled task.

Tests

TaskProcessingTest::testScheduleTaskWithOmittedOptionalFileInput schedules a task type with an optional File input slot, omits the slot, and expects the task to reach STATUS_SCHEDULED.

References #60218

Cross-references

• fix(TaskProcessing): Normalize file ID before getting node #60218
  • open, patches the exact crash site, throws instead of skipping absent slots
• fix(TaskProcessing): Harden task scheduling with webhooks #63687
  • merged, webhook validation in prepareTask, no null-optional handling
• fix(taskprocessing): AppAPI webhook error handling #62597
  • open, runWebhook error handling, unrelated to slot resolution

---

_{Assisted by opencode with zai/glm-5.3, reviewed by WSHAPER}