You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(cli,core,webapp): fail dev and deploy on duplicate task ids
Two tasks defined with the same id — including across task types (e.g. a
scheduled task and a regular task sharing an id) — previously caused the
second definition to silently overwrite the first in the resource catalog,
so one task would vanish with no warning.
Detect collisions at registration time in StandardResourceCatalog (the only
point where both definitions are visible before the id-keyed map collapses
them) and fail indexing via a new TASKS_FAILED_TO_INDEX message that names
each offending id and the files it was found in. This blocks both `dev` and
`deploy`. The same rule is enforced server-side when the background worker is
registered, as a backstop.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
`dev` and `deploy` now fail with a clear error when two tasks are defined with the same id, including across different task types (e.g. a scheduled task and a regular task sharing an id). Previously the second definition silently overwrote the first, so one of the tasks would vanish with no warning. Task ids are detected as duplicates during indexing (naming each offending id and the files it was found in), and the same rule is enforced server-side when the background worker is registered.
`Duplicate task ids detected: ${details}. Each task must have a unique id across all task types (including scheduled tasks). Please rename one of them.`,
0 commit comments