Loop issue and REST API trigger issue

After upgrading to 2.0, most of the things were going well until I tried to migrate most of the things from Zapier or other platforms like that that to BuildShip.

Below are the two biggest challenges I faced:

Loop
Loop node is not consistent. I have a list of 300 contacts
I tried to loop each one of the contacts and send an email to them via SendGrid
I have 3 nodes (airtable retrieval node, branch node, SendGrid node) in a loop
Only the first node in the loop is triggered (Get a Record in Airtable, the retrieval node)
The rest of the nodes did not get triggered at all
My setting for the concurrent rate is "1"
REST API trigger
Due to the loop issue, I opted for an alternative solution
have only 1 node within the loop, which is to send an HTTP request to trigger another workflow (send one email via SendGrid, on one Airtable record, one at a time), lets call it "SendGrid Workflow"
While the HTTP request was triggered successfully 300 times, most of them failed to trigger the "SendGrid Workflow" to send the emails out
the success rate of triggering the "SendGrid Workflow" was 30 out of 300, 10%, 90% failed

I got very frustrated as I am not using this to send marketing email, rather, I am send email for important date reminders and etc. Without consistency, cannot reply upon it.

I got the workaround, which is to use a platform like Zapier to send each record from Airtable to trigger "SendGrid Workflow" with a 2 seconds interval in between each request. This worked well with 100% success rate.

I hope someone can help me rectify this without me having to go through another platform to do so. Thanks.

AI Support•1/14/25, 4:28 AM

AI Support Bot Information

@1062213785990991972 you can react on the relevant answer (message) with a

in this thread when you think it has been solved, by the bot or by a human!

Anyone can react on this message with a

if the GPT bot is unhelpful or hallucinating answers.

Please note: Team members will review and answer the questions on best efforts basis.

AI Support•1/14/25, 4:29 AM

AI Response

It seems you've been experiencing some challenges with using the Loop node and REST API trigger in BuildShip. Based on the issues you described, here are some insights and potential solutions:

**Loop Node:**
- Ensure that the Loop node is correctly configured to handle multiple iterations. Double-check that the loop logic and nodes are properly set up to execute actions for each item in the list.
- If the Loop node is somehow terminating early or skipping steps, verify that there are no errors in the logic or any conditions that might cause the loop to exit prematurely.
- Consider breaking down the loop process into smaller parts or adding logging/debugging statements to monitor each step's execution, which might help identify where the issue occurs.
**REST API Trigger:**
- When using REST API triggers for sending requests to another workflow, ensure that the receiving endpoint is fully capable of handling concurrent or rapid requests. If it's not scaling properly, some requests might fail.
- Consider implementing a queuing mechanism or rate-limiter to pace out the requests. This mirrors your successful workaround on Zapier, where you introduced a 2-second interval between requests.
- If possible, increase the resources allocated to the "SendGrid Workflow" to handle more requests concurrently without failing.
- Re-evaluate the error logs to understand better what causes the failures in the triggered workflow (e.g., timeouts, unauthorized errors).

If you are still facing challenges, please consider reaching out to the BuildShip support team through in-app support for more personalized assistance.

BuildShip AI Support

•

1/14/25, 4:29 AM

jeff_sssOP•1/14/25, 4:30 AM

By the way, my concurrent rate was set to 1

jeff_sssOP•1/14/25, 4:40 AM

Based on the Builship AI support, I have the following two points:

There are no areas to set the "rate limit" in the trigger
There is no guidance as to where I can set the delay for each loop just like I did in Zapier.