Luckyrolls - Buildship is down for me. Worki...
Buildship is down for me. Working on a new app and today I was putting together a flow to demonstrate how BuildShip can be better alternative than an Edge function of our backend needs which would have been tomorrow moning.. And now ... been down over over three hours with no response from support. 😦 All my flows freeze
3 Replies
@Luckyrolls we have sent you an email few minutes ago could you please check? Also it seems that you are using a custom node in which the node logic is faulty which is throwing 429 too many request error.
You can followup on the email.
You will see my response. I only had one node that was looping, rewrote some of the code and put in a limit to its iteration (although there was no obvious spot causing the problem - it seemed to be working). Is there anyplace in the environment that can give me a clue to the troublesome node? Although I have updated this node, I don't really know that it was the problem.
Oh - and you didn't say, but I assume it was a buildship request generating the 429, not a supabase call because I looked at the Supabse logs and there were no 429s.
Thanks for sharing the previous code. The error 429, 'Rate limit exceeded,' was not due to Supbase, instead, it was caused by the custom node logic generated by ChatGPT on the waitedRR node. If you take a look at this line of code in your old (legacy) code logic, finalMLP.length < maxItems && iterations < 1000, it can cause an iteration up to 1000 until break, and by default, the BuildShip API timeout is 300 seconds.
Thank you for confirming that the updated node logic is functioning well for now. Also, please note that we recommend using the inbuilt AI Builder to create custom nodes instead of using an external LLM to generate logic, as this could lead to issues. The BuildShip LLM for AI Builder is designed to manage and prevent infinite or non-terminating long conditions.