From 81a5c5fb7d5be963c9f6734b0bb887ae454a213c Mon Sep 17 00:00:00 2001 From: Jeremy Daer Date: Fri, 31 Jul 2026 08:28:17 -0700 Subject: [PATCH] Deprioritize is exact-target; repeat-DELETE is a no-op Mirrors bc3 #12483 (d0edc128): the DELETE clears only the priority carried by the recording the URL identifies, deleting an absent priority is a no-op 204, and surfaced steps are addressed by their priority_recording_id. --- sections/my_assignments.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sections/my_assignments.md b/sections/my_assignments.md index 2d62b71..b238bab 100644 --- a/sections/my_assignments.md +++ b/sections/my_assignments.md @@ -690,6 +690,8 @@ Deprioritize an assignment * `DELETE /my/priorities/1069479801.json` removes the recording with an ID of `1069479801` from Up Next. Returns `204 No Content`. +The delete is **exact-target**: it clears only the priority carried by the recording the URL identifies, and deleting a recording that carries no priority is a **no-op** that still returns `204 No Content` — so a repeated `DELETE` (a client retry after a lost response) is safe and never touches any other priority. To deprioritize a card table step surfaced under its parent card, send the step's own id — the `priority_recording_id` reported by [Get assignments](#get-assignments) — not the card's id. + ###### Copy as cURL ```shell