Vibe App Performance Limits, vibe-auth Gateway, and HTTP 429 "Slow Down" Errors

Hi,

I'm building a comprehensive portfolio planning tool on Monday Vibe that manages and synchronizes data across four connected boards.

When the application runs batch updates across these boards, we frequently encounter connection timeouts and HTTP 429 ("slow down") responses. The performance we're seeing appears significantly lower than the standard Enterprise API limits we would expect.

Based on review of the request flow and diagnostics, it appears these responses may be occurring during Vibe server function (_serverFn) requests and could be related to the vibe-auth layer or another Vibe platform component rather than the underlying Monday GraphQL API itself. However, we're looking for clarification from the Monday team on whether this is the case.

Our understanding of the Enterprise limits is:

• 5,000 requests per minute

• 25,000 requests per day

• Multiple changes can be batched into a single request

• Requests are also subject to complexity limits

Could someone help clarify:

1. Are there any published rate limits, concurrency limits, execution limits, or timeout thresholds that apply specifically to Vibe apps or _serverFn requests?

2. Does the vibe-auth layer (or another Vibe platform gateway) impose throttling independent of standard Monday API limits?

3. Are there recommended batching or architecture patterns for apps that perform large multi-board updates?

4. Are there plans to expose these limits or provide monitoring so developers can identify which limit is being hit when 429 errors occur?

Any documentation or guidance would be greatly appreciated.

Thanks!