Relay sync path misclassifies update/deactivate flows as create flows #55

New Issue

2026-04-30T16:34:06Z

userAdityaa commented

2026-04-30 16:34:06 +00:00

The update and status mutation logic incorrectly resets synced = 0, causing the system to treat existing relays as new. This forces create behavior (POST + secret regeneration) even during updates, instead of using PATCH with no secret changes.
As a result, updates or deactivations may fail if POST is strictly create-only, or worse, repeated secret regeneration can cause relay identity and credential drift.

The update and status mutation logic incorrectly resets synced = 0, causing the system to treat existing relays as new. This forces create behavior (POST + secret regeneration) even during updates, instead of using PATCH with no secret changes. As a result, updates or deactivations may fail if POST is strictly create-only, or worse, repeated secret regeneration can cause relay identity and credential drift.

userAdityaa referenced a pull request that will close this issue

2026-05-01 10:10:24 +00:00

fix: relay sync create/update classification to prevent false create mode on updates #56

hodlbod closed this issue

2026-05-01 14:21:38 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coracle/caravel#55