Sign-in, access and outages

What does "We are experiencing an unusual surge in the number of requests" (HTTP 429) mean?

Your account went over its per-minute API rate limit; wait, then reduce or throttle the integrations and scripts that call the API.

Fix

Short answer: Your account went over its per-minute API rate limit, so Kissflow throttled it. Wait a few minutes, then reduce how many calls your integrations and scripts make.

Why it happens

  • The limit applies to the whole account domain. Calls over it return HTTP 429 with KISSFLOW_ERROR_15009.
  • Integrations, button scripts and other automations are the usual source of the calls.
  • Frequent identity syncs that push many users and groups can add to the load.
  • A 429 that comes back from a third-party URL is that system's own limit, not Kissflow's.

How to fix it

  1. Wait a few minutes and try again. The throttle is temporary.
  2. Find the integrations, scripts and automations that call the Kissflow API. Run them less often, or add batching and delays so they stay under the limit.
  3. Handle 429 responses in your own scripts and retry later. In an integration, you can switch on Auto retry in the integration header. It retries a step that failed with Too many requests up to four times over about three minutes. Use it only where repeating the step is safe, because a retry can create duplicates.
  4. If you provision users through SCIM or directory sync, sync less often.
  5. If Cloudflare blocks a request because of a security rule, change the request payload on your side.
  6. If it keeps happening, contact Kissflow support with the times it happened. To ask for a higher limit, go through your Kissflow account manager.

Important

One busy integration can trigger this error for every user in the account. The exact limit can differ by account or plan, so confirm yours with your account manager.

Related answers