Skip to content

Bind conversation invocation atomically before metered assignment execution #440

Description

@adrianwebb

SDK golden CB workday-9d11e917-f795-4c71-9b1e-89459fb383a7 stopped after providers.assignments.discussion.respond could not find invocation-c5075651da4d671050409fa9f8810385 bound to assignment_lLcc1c7sifGL8zeVLXbFYXLDN2oNrTYu. The assignment and invocation existed, but admission had no assertion that its invocation UPDATE affected a row. Keep one admission path: lock and guard the invocation before reservation, allow rebinding only from a terminal attempt for that same invocation, and fail early with observed binding/status if custody is lost. Focused admission regression and full API tests required; live automated golden remains unpassed. Detailed campaign evidence: Platform #520.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions