Cause
This idempotency key already identifies a different request body for the same operation. Guile replays or rejects based on the first request; it does not run your new parameters and does not create a second write.Fix
Retry the original request unchanged to get the first result, or use a new idempotency key when you mean a different write.Retry safety
Safe to retry with a new idempotency keyRaised by
These operations can return this problem:- Create an appointment
- Confirm a booking request
- Decline a booking request
- Add a payment method
- Prepare a payment method