We are getting 504 errors from the Pactflow API. C...
# pactflow
s
We are getting 504 errors from the Pactflow API. Could anyone look into this?
m
Could you please raise a support ticket so we can track it? howtopactflowsupport
s
Please create a ticket here with the issue details so that we can properly track the resolution and the PactFlow product support team will continue to work through it with you: https://support.smartbear.com/pactflow/message
m
I don't see any issues with our monitoring could be specific to your account or something else.
s
I would rather want to avoid creating another ticket with your customer service. I did that when we had a problem with 502 errors from Pactflow in the past and they were not able to solve the issue (to put it mildly).
m
what’s your tenant? Gateway timeouts are usually due to data complexity and certain queries timing out. We are aware of some performance issues which we are working on (mostly related to matrix e.g. https://github.com/pact-foundation/pact_broker/pull/631) Are you seeing them via certain API calls?
s
Sent tenant and more details in a direct message. We got the 504 when loading a Pact before verification. Thanks for you help, Matt!
m
FYI I have created https://github.com/pact-foundation/pact-jvm/issues/1710 to track this issue. The HTTP client should be retrying, but because the request is not considered a safe one to retry (its idempotency strategy) it gives up. I think we just need to not use the Apache client default retry strategy. Given the number of `504`s should be (and were) very low, this is a good solution to provide resiliency in the system. Please follow that ticket for progress