https://pact.io logo
Join Slack
Powered by
<@U9UUY3CU9> different problem this time, I’ve got...
# pactflow
m
@Matt (pactflow.io / pact-js / pact-go) different problem this time, I’ve got a 404 trying to record a pact to the following endpoint: 
/pacticipants/saq-summary-etl/versions/4b4c8962c8f7243a28cdeda7cbcbf7b7d90ae41a/deployed-versions/environment/6433116c-b3cd-48ce-bd0d-ed2a12b844ee
- any ideas? The response is:
Copy code
404 . {"error":"The requested document was not found on this server."}
In the old UI I might attempt to find the version using your API, but I can’t find that on the new UI.
if I try to switch branches on this UI screen I get the same branch in the dropdown, Idk if something is broken with this pact or if its the UI thats broken.
here’s a recording of the behaviour. It could be unrelated to my broken POST or it could just be a coincidence
Screen Recording 2025-07-09 at 15.38.35.mov
No its the same behaviour on all of the applications. so its not the same problem
m
I’ve got a 404 trying to record a pact to the following endpoint: 
/pacticipants/saq-summary-etl/versions/4b4c8962c8f7243a28cdeda7cbcbf7b7d90ae41a/deployed-versions/environment/6433116c-b3cd-48ce-bd0d-ed2a12b844ee
- any ideas?
How are you making that call Matt? i.e. what command/API are you running to record the deployment?
RE: the video, thanks for that. It looks to be a bug - I’ve raised a request to get that fixed ASAP
(from what I can tell, it looks to automatically re-select the last item in the branch drop down - but the selected branch is correct)
Should be fixed now Matt - thanks!
m
> How are you making that call Matt? i.e. what command/API are you running to record the deployment? we are using an http4k HttpHandler POST call from code sending content-type of 
application/json
. It works for all our other deployments except this one. I suspect that some state is incorrect on the pact broker, but I can’t work out why.
Should be fixed now Matt - thanks!
wonderful 🙂
@Matt (pactflow.io / pact-js / pact-go) I still can’t send that POST to the endpoint..
m
Are you following the HAL resources, or directly hitting the URL?
👀 1
(I should clarify, the fix was for that UI quirk)
✅ 1
Are you sure that version exists?
m
> Are you following the HAL resources, or directly hitting the URL We don’t follow the HAL resources, we GET the relevant environment’s id from your endpoint 
/environments
using its name , and then POST > Are you sure that version exists? > > [11:41 AM] > i.e. if you head to https://sdx.pactflow.io/pacticipants/saq-summary-etl/versions/4b4c8962c8f7243a28cdeda7cbcbf7b7d90ae41a in the UI, do you get a web page? No, 404. So I wonder how we can get into that state. We use a commit hash to identify the version being built, and its possible the commit hash wasn’t created as a version in pact. Thanks for the info, I might be back!
👍 1
m
A quick search of our logs, suggests all 
PUT
s to 
/pacticipants/saq-summary-etl/branches/master/versions/4b4c8962c8f7243a28cdeda7cbcbf7b7d90ae41a
resulted in `429`s
In case it’s helpful (`429`s over the past few weeks)
It looks like you’ve got some bursty thing going on. 2k+ API calls in 10s is likely to get you throttled.
exactly 5 minutes early, about 2.5k calls.
m
yes we know about that problem. It happens when our monorepo gets built by a commit in a common library or code path, and all our services get deployed at one time. It also floods our environment with deployments and k8s has a hard time too. Thanks for pointing the PACT 429 out as well, I will add it to our ticket to fix it.
👀 1
👍 1
Open in Slack
PreviousNext
Powered by