This is more of an open question for anyone browsing through the issues:
Has anyone ever gotten this error?
Transaction AUVtEbv4kJqX55ZqZnh3keyazlAoT31Or4etT6xwIDzUW9rXPitoPRnz2nXYtLXBrvrR/O11yevkSDOYZpx1v8ezMAzq/SwaJVL6rF93qZFHpGBYTLlPMZpvDcYZRqDfR5nDB38ZHQLKnvz/76tsJcxEaDnprz9jNbo1gNpmtGCzQDJfqKTNehx6hun57KCuFkqHjxO8pTrd is not found
It's a one-off error; that is, the code hasn't changed, literally only one user ever has gotten this error.
This is more of an open question for anyone browsing through the issues:
Has anyone ever gotten this error?
Transaction AUVtEbv4kJqX55ZqZnh3keyazlAoT31Or4etT6xwIDzUW9rXPitoPRnz2nXYtLXBrvrR/O11yevkSDOYZpx1v8ezMAzq/SwaJVL6rF93qZFHpGBYTLlPMZpvDcYZRqDfR5nDB38ZHQLKnvz/76tsJcxEaDnprz9jNbo1gNpmtGCzQDJfqKTNehx6hun57KCuFkqHjxO8pTrd is not found
It's a one-off error; that is, the code hasn't changed, literally only one user ever has gotten this error.
The queries are 100% valid, and if I grab those exact queries from Sentry and run the transaction manually in Postgres, it runs fine.
I'm guessing this might be a hiccup on Amazon's end, not necessarily an issue with the Data API Client.