Raised in strict resume mode when a resume doesn't match the pending interrupts.
reason says how it doesn't match:
"not_pending": the resume names interrupts that aren't pending, listed in
interrupt_ids."empty_map": the resume is an empty map."ambiguous": the resume is a single value while several interrupts are
pending.pending_ids lists the interrupts still waiting for an answer. The error is
raised before anything is written, so they can still be answered.
A single value with no interrupt pending is accepted, because it resumes a
graph paused at a static breakpoint (interrupt_before or interrupt_after).
The interrupts one task raises share an id, so an answer retried after the task asked its next question answers that question.