Skip to main content
Quick Summary: The request is well-formed but the current state of the resource refuses it — most often a guarded delete. The body extension members tell you exactly what stands in the way.

​
What happened

Common cases:
  • Deleting a career that still has sections, skills, levels or assigned people. The body carries confirmRequired: true and a dependencies object with the counts. Retrying with ?confirm=true performs the delete anyway.
  • Deleting a career level where people are assigned at that level. The body carries wouldUnassignPeopleCount — deleting unassigns those people from the entire career. Retry with ?confirm=true to proceed.
  • Deleting a career type that careers still use.
  • A concurrent request with the same Idempotency-Key is still executing — retry shortly to receive its stored response.

​
What to do

Read the extension members, decide deliberately, and — for guarded deletes — retry with ?confirm=true only when the reported consequences are acceptable.