- Issue created by @carsoncho
- Assigned to Prashant Mishra
- Status changed to Needs review
7 months ago 9:10am 28 May 2024 - Status changed to Fixed
7 months ago 5:39pm 31 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.
As noted in 🐛 Caller reference is not unique per request Postponed: needs info when for example triggering a bulk update we sometimes receive this error.
Error executing "CreateInvalidation" on "https://cloudfrontxxx/2020-05-31/distribution/.../invalidation"; AWS HTTP error: Client error: `POST https://cloudfront.amazonaws.com/2020-05-31/distribution/.../invalidation` resulted in a `400 Bad Request` response: <?xml version="1.0"?> <ErrorResponse xmlns="http://cloudfrontxxx/doc/2020-05-31/"><Error><Type>Sender</Type>< (truncated...) InvalidArgument (client): Your request contains a caller reference that was used for a previous invalidation batch for the same distribution. - <?xml version="1.0"?> <ErrorResponse xmlns="http://cloudfront.amazonaws.com/doc/2020-05-31/"><Error><Type>Sender</Type><Code>InvalidArgument</Code><Message>Your request contains a caller reference that was used for a previous invalidation batch for the same distribution.</Message></Error><RequestId>...</RequestId></ErrorResponse>
Change the caller reference to be more accurate. Like hash of paths to invalidate + timestamp.
Fixed
3.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.