Kissflow won't load, is slow, or shows "There was an error. Reload" or 403. What do I do?

Short answer: If everyone in your account is affected, it's likely a platform incident that Kissflow fixes on its side. If only you are affected, clear your cookies and cache, then try another browser or network.

Why it happens

• Platform incidents or upstream cloud outages affect every user until Kissflow fixes them.
• Stale cookies or cache, often left after a platform update, cause errors for one user.
• An outdated browser, a firewall, a VPN or an ISP block can stop pages from loading.
• Kissflow's network security layer can block requests before they reach the app.
• "Unusual surge in the number of requests" means your account sent too many API calls.

How to fix it

1. Ask other users in your account whether they see the same problem. If everyone does, wait for Kissflow to fix it.
2. Clear Kissflow's cookies and cached files for All time. Close the browser completely, reopen it and sign in again.
3. Open Kissflow in an incognito window, another browser, or on another network such as a mobile hotspot.
4. Update your browser. Kissflow supports Chrome, Edge and Firefox 120 and above, and Safari 17 and above. See supported browsers.
5. If it fails for everyone in your office, ask IT to whitelist the domains in ensuring smooth access to Kissflow, and try without a VPN or proxy.
6. If you see an "unusual surge" error, stop scripts or integrations that call the API in bulk. See the related rate-limit answer.
7. If you see a message that the account is blocked, ask your billing owner to check for pending payments.

If none of this helps, contact Kissflow support with the page URL, the exact time and time zone, a screenshot or recording, and your debug session key. To find it, click your profile picture > My settings > API authentication > Debug session key > Show. See API authentication.