Caller reference is not unique per request

Created on 30 April 2024, 7 months ago
Updated 14 June 2024, 5 months ago

Problem/Motivation

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>

Proposed resolution

Change the caller reference to be more accurate. Like hash of paths to invalidate + timestamp.

🐛 Bug report
Status

Fixed

Version

3.0

Component

Code

Created by

🇺🇸United States carsoncho Kansas City, MO

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024