Skip to content

Deprioritize is exact-target; repeat-DELETE is a no-op #428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremy merged 1 commit into from
Jul 31, 2026
+2 −0
Merged

Deprioritize is exact-target; repeat-DELETE is a no-op #428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions sections/my_assignments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading