Zoho Desk disconnection. 'My Zoho Desk connection'. Status Code Error: 400'

Features
, ,
1

Scenarios randomly fail to run due to a disconnection. There’s no fixed time limit, as after re-authentication, I can sometimes run the same scenario several times in a row, and other times it only works once.

I can’t figure out why. Time? Trying too hard? Errors?
Does anyone else have the same problem? I have other connections with other products, and it doesn’t happen.

Error

Cannot initialize the scenario because of the reason ‘Failed to verify connection ‘My Zoho Desk connection’. Status Code Error: 400’

  • - Failed to verify connection ‘My Zoho Desk connection’. Status Code Error: 400
3

Based on the error message, your scenario is failing because the Zoho Desk API is rejecting the connection request. The 400 status code stands for a “Bad Request,” which means the API received a request that was malformed, incomplete, or invalid in some way.

The Problem

The most likely cause for this intermittent failure is a rate limit or an expired/corrupted access token. While Make.com automatically manages token refreshes, if the refresh process fails or your scenario is making requests too quickly, the Zoho Desk API can return a 400 error to prevent abuse. The fact that it works sometimes and fails at other times points directly to an issue with the timing of your requests.

Direct Solution

To fix this, you should re-establish the connection and add a delay and a retry handler to your scenario.

  1. Re-authenticate the Connection:

    • In the Zoho Desk module that’s failing, click on the connection dropdown.

    • Click Add to create a new connection, and follow the steps to re-authenticate with your Zoho Desk account. This will ensure you have a fresh and valid token.

  2. Add a Delay Module:

    • If your scenario is running in a loop or processing multiple items at once, add a Flow Control > Delay module before the Zoho Desk module.

    • Set the delay to at least 1 second. This will space out your API calls and prevent you from hitting the rate limit.

  3. Implement an Error Handler:

    • Right-click on the Zoho Desk module and select Add error handler.

    • Choose the Retry option. Set it to retry the request up to 3 times with a short delay (e.g., 15 seconds).

This will make your scenario more resilient. When a temporary issue like a rate limit occurs, Make.com will wait and try again instead of failing.

4

Hi! Thank you so much!
It’s true that I kept adding Zoho modules to the same scenario, and that’s why the 400 error kept getting worse. Following your advice:

I added some “Tools => Sleep” modules — just in case someone else reads this and finds it useful, since I didn’t have “Delay” available.

Although that helped reduce the impact of the 400 error in smaller scenarios, in others with many modules, the Sleep didn’t help during the initialization phase, so a lot of requests were already being made before the execution started.
To work around that, I split the process into several smaller scenarios whenever possible, and in those smaller segments, I created one connection for every three modules.

It’s not very elegant, but it works.

1 Like