Antoine - Has anyone else had any trouble with ...
Has anyone else had any trouble with the Buildship HTTP request trigger node since the end of last week?
Some of mine don't show any disconnection on the interface, but for unknown reasons they aren't accessible from my front end anymore. With litterally no change (endpoint, node, ...). In this case, I don't have any logs on Buildship.
I'm working on an production app, so it's kind of annoying
16 Replies
Hi @Antoine, but for unknown reasons they aren't accessible from my front end anymore.when you run/hit your endpoint/webhook url from frontend? What response you get?
Hello Gaurav,
I got a 400 (not sure about which 40* I have). And I need to click on the "Connect" button in the HTTP node to make it works again.
the process is - click
connect then ship. 400 can result in lots of issues, you can submit it via in-app support..I've again the error (but it worked this morning during like 1hour...) so I can tell you more about it :
Error 404
"Workflow not found, make sure you have deployed it with the trigger method set to GET and path set to /coaches/XXXX/slots/XXXX"
But :
this looks correct, you'll have to ensure you're making a GET request only to the above URL with the path variable
:slotId otherwise it will give this error. https://docs.buildship.com/triggers/path-variable
The error is also validRest API Path Variable – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
It's what I do :
What’s in response, this is request not found..
Can you share this flow via in-app support, we can make sample call to test this.
@Gaurav Chadha message sent!
FYI, I'm not sure but I think it could be from workflows folders. If I move a workflow from 1 folder to another one, sometimes I've got the same problem
and it seems that I've the problem only with my GET endpoints
thanks for sharing, we're checking the issue, will update you on the fix.
@Antoine you’ll be required to use
* in all their paths that start with /coaches.
/coaches/:coachId/slots/:slotId becomes /coaches/*/slots/*Thanks @gauravc !
How can I use * as input ? Like I did before with PARAM.slotId
Yes, it will read all
Hello @Gaurav Chadha, I didn't understand how I can keep using params data in your message.
In this case, I have 'coachId' and 'offerId' in my endpoint, which I use as input in my workflow. If I replace both of these with '*', how can I read the specific parameter?
I'm using params as an object containing elements. I don't know if this is the right way, but it's working!
Erratum : it's not working
only one parameter has been read...
Hi @Antoine you have /coaches/:coach_id/offers/:offer_id and /coaches/:coachId/slots/:slotId paths. These two paths start the same, with /coaches, but then use different names for the second parameter, which is a current limitation.
Both paths should have coachId, coach_id, or simply *. You'll be required to have different starting paths.
We've sent you an email reply to your support request, we can followup on email
Hi Gaurav, everything seems to be working now that you've given me this solution. Thank you so much for your response!