Error while hydrating data from Trello: Process exited before completing request

Hi ​@jrosseau,

Welcome to the Community.

If you're experiencing increased error rates with Trello in Zapier, check for API rate limits, as exceeding them could cause failures. Review any indirect changes in data volume or integrations that might impact the Zap. Examine Zap history for error patterns, and try reauthorizing the Trello connection to resolve authentication issues. If handling large amounts of data, optimize performance by using filters or breaking workflows into smaller Zaps. Finally, error-handling strategies like retries or notifications should be implemented to improve reliability.

I hope these steps help you address the increased error rate with your Trello integration. If you have any more questions or need further assistance, feel free to ask.

A few questions and thoughts.

My volume of usage, nor the Trello card contents have not increased, but I noticed the error occurence increasing.

Where would I check the API rate limits.  I have tried asking the virtual support bot and it did not provide adequate guidance.

In terms of retries and notifications, are their readings you might suggest to hunt those down?

Hi ​@jrosseau,

Before we dig deeper into this, could you please let us know the trigger you’re using? This will help me take a closer look at the issue.

Thanks!

Sure, it is when a Trello Card is moved to a specific list.

Thanks for the screenshot ​@jrosseau!

So it looks like the cards failing to process due to the error: Error while hydrating data from Trello: Process exited before completing request have files that are too heavy to process within 30 seconds. For reference, Zapier typically waits for 30 seconds for each step in a Zap to complete. If it takes longer than that, a similar error to the above comes up. 

Do you know how heavy the attached file is? An alternative here would be to include a link to the file instead of the file itself.

I'll be keeping an eye out for your response!

That is probably the issue then.  As these cards are associated with music submissions from artists, sometime they are mp3 files which can be 5MB or less, but sometimes they are WAV files, which can be 30MB or more….easily.

Hi ​@jrosseau,

Thanks for the update here.

Have you tried replaying the errored runs to see if it’ll go through? If not, I’d recommend reaching out to our Support Team since they have the correct tools to dig deeper in the Zap and its logs.

You can reach our Support Team here: https://zapier.com/app/get-help

Hopefully, this helps!