- Merge request !1Issue #3304477: Caller reference is not unique per request → (Open) created by eyilmaz
- 🇺🇸United States superrn
We are seeing this often on a new project that we are deploying with this purger. Is there a proper fix for this?
We sometimes get the following error:
Your request contains a caller reference that was used for a previous invalidation batch for the same distribution.
purger_cloudfront_xxx: Aws\CloudFront\Exception\CloudFrontException: Error executing "CreateInvalidation" on "https://cloudfrontxxx/invalidation"; AWS HTTP error: Client error: `POST https://cloudfrontxxx/invalidation` resulted in a `400 Bad Request` response: <?xml version="1.0"?> <ErrorResponse xmlns="http://cloudfront.amazonaws.com/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. [...]
Change the caller reference to be more accurate. Like hash of paths to invalidate + timestamp.
Postponed: needs info
1.2
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
We are seeing this often on a new project that we are deploying with this purger. Is there a proper fix for this?