Frequently face time out errors when using Bika API

Bika.ai discussions
1

I use API/Automation quite a lot.
I notice “timeout of 60000ms exceeded” is happening almost everyday.
Hope you investigate the root cause and fix them completely. Thanks.

image
image1583×677 204 KB

2

Hey @vincentlo, thanks for sharing the screenshot! Looking closely, it seems you are using a Make.com (Integromat) HTTP module to send a PUT request to our OpenAPI v2 (https://bika.ai/api/openapi/bika/v2/spaces/...).

The timeout of 60000ms exceeded (a 500 Internal Server Error) means our backend couldn’t finish processing your request within the 60-second execution time limit.

Usually, this happens in two scenarios:

  1. Massive Payload: Are you trying to update an extremely large number of records in a single bulk PUT request?
  2. Heavy Computations: Does the target datasheet contain complex formula dependencies or cross-sheet rollups that trigger massive cascading calculations upon update?

If it’s a bulk update issue, I highly recommend breaking the payload into smaller batches (e.g., 50-100 records per request) in Make.com.

Could you share the complete API endpoint path you’re calling and the approximate size/structure of your request body? That will help us dive into the server logs and pinpoint the exact bottleneck for you.

3
  1. Not massive paypload: I ran single put request per one record change, normally I don’t try to update an extremely large number of records
  2. Is changing 10 records via 10 different requests per 1 minute considered “**Heavy Computations **”?
4

Hi @vincentlo,

Thanks for the clarification. 10 requests per minute (updating 1 record each time) is a very low frequency, which normally shouldn’t cause a timeout issue on its own.

To help us understand the situation better, could you share a bit more about the specific table you are updating in Bika?

  1. What is the approximate data volume (total number of rows) of that table?
  2. How complex is the table structure? Are there many complex formulas, linked records, or cross-sheet rollups? Sometimes, updating even a single record can trigger heavy cascading calculations across the database.

Also, as a temporary workaround, you might want to check if there is an option in the Make.com HTTP module to increase the timeout limit setting.

Looking forward to your reply so we can understand the context better!