Open lukeduran opened 3 months ago
The error in this ticket is specific to Washington, DC. There are several other regions that would result in this same issue. The solution is drafted and in the queue for implementation behind a couple other more important issues.
This request is passing in our v2.0.0 development environment.
I believe that we previously faced an issue very similar to this, but I'm creating a new issue because we are still facing this quite a bit - unsure if they are related. Below is both a request and the response we received. I have at least 14 of these that I can share if it would be helpful.