Skip to main content
Performance problems can stem from your network, your browser, a large workspace, or an active platform incident. Work through the section below that matches what you’re experiencing — most issues have a clear diagnosis path before you need to contact support.
If fsckmsft pages are taking more than a few seconds to load, start with these checks before assuming the problem is on our side.1. Check the status pageVisit status.fsckmsft.org first. If there is an active incident affecting the web application or API, our team is already working on it. Subscribe to updates and wait for the Resolved status before troubleshooting further.2. Test your internet connectionRun a speed test at fast.com or speedtest.net. fsckmsft requires a stable connection of at least 5 Mbps for a comfortable experience. If your connection is slow or unstable, that’s the root cause.3. Try a different browserSwitch to a different browser to isolate whether the issue is browser-specific. Chrome, Firefox, Edge, and Safari are all fully supported. If another browser loads faster, the issue is with your primary browser’s profile or settings.4. Disable browser extensionsExtensions — especially ad blockers, VPNs, and developer tools — can significantly slow down page load times by intercepting network requests. Disable all extensions and reload fsckmsft. If performance improves, re-enable extensions one at a time to find the culprit.5. Check your VPN or proxyIf you’re connected to a corporate VPN or proxy, try disconnecting temporarily. VPNs route traffic through additional hops and can introduce latency, especially if the VPN server is geographically distant from fsckmsft’s infrastructure.
If slow loads only happen at certain times of day (e.g. during peak office hours), the issue is likely network congestion at your location or ISP rather than fsckmsft infrastructure.
fsckmsft’s document editor is optimised for workspaces of up to 500 blocks per document. Beyond that threshold, you may notice:
  • Typing lag (keystrokes appear delayed)
  • Slow cursor movement
  • Sluggish block reordering
  • Delayed autosave indicators
Split large documentsThe most effective fix is to split oversized documents into smaller, linked ones.
1

Identify the large document

Open the document and scroll to the bottom. If it contains hundreds of blocks (paragraphs, headings, images, embeds), splitting is recommended.
2

Create new documents for logical sections

Cut content from the bottom half of the document and paste it into a new document. Use descriptive titles so you can find each part easily.
3

Link the documents together

At the top or bottom of each document, add a link to the related documents so readers can navigate between them.
Other editor performance tips
  • Collapse unused sections — folding large toggle blocks reduces the rendering load.
  • Remove unused embeds — embedded iframes and videos are expensive to render. Remove embeds you no longer need.
  • Avoid pasting rich text from Word or Google Docs — paste as plain text (Ctrl+Shift+V / Cmd+Shift+V) then re-format, to avoid importing excess markup.
If you’re experiencing lag in documents well under 500 blocks, it may be a browser memory issue. Try closing other tabs or restarting your browser.
If your automations (workflows, triggers, scheduled jobs) are taking longer than expected to execute, check the following:Check your plan’s rate limitsAutomation execution is subject to rate limits that vary by plan:
PlanAutomation runs per hour
Free50
Pro500
Business5,000 (custom limits available)
If you’re hitting your rate limit, runs are queued and execute as capacity becomes available. Upgrade your plan or optimise your automations to reduce execution frequency.Check for failed or looping automationsA poorly configured automation that loops or repeatedly retries on failure can consume your run quota and slow down other automations. Go to Settings → Automations → Execution Log and look for automations with high failure rates or unusually high execution counts.Review external API dependenciesIf your automations call external APIs or webhooks, slowness may originate from those external services, not from fsckmsft. Check the execution log for high response times on external steps.Check the status pageAutomation infrastructure is listed as a separate component on status.fsckmsft.org. If the Automations component shows degraded performance, our team is aware and working on it.
If the steps above haven’t resolved your performance issue, contact support with a HAR file — a recording of all network requests made during the slow experience. This is the single most useful thing you can provide.Capture a HAR file in Chrome
1

Open Chrome DevTools

Press F12 (Windows/Linux) or Cmd+Option+I (macOS) to open DevTools, then click the Network tab.
2

Enable 'Preserve log' and clear the log

Check the Preserve log checkbox at the top of the Network panel. Then click the clear button (🚫) to remove any existing entries.
3

Reproduce the slow behaviour

Perform the exact action that is slow — load the page, open the document, or trigger the automation — while the Network panel is recording.
4

Export the HAR file

Right-click anywhere in the network request list and select Save all as HAR with content. Save the .har file to your desktop.
5

Attach to your support ticket

Email support@fsckmsft.org with the HAR file attached. Also include:
  • A description of the slow action
  • The approximate time and date the issue occurred
  • Your browser and OS version
  • Your workspace URL
HAR files can contain sensitive information including authentication tokens and response bodies. Send HAR files only to support@fsckmsft.org and avoid sharing them publicly or in community forums.
Capture a HAR file in FirefoxOpen DevTools (F12), go to the Network tab, reproduce the issue, then click the gear icon → Save All As HAR.Capture a HAR file in SafariEnable the Develop menu (Safari → Preferences → Advanced → Show Develop menu), open Develop → Show Web Inspector, go to the Network tab, reproduce the issue, then click Export (the down-arrow icon).
Performance issues that are intermittent or time-of-day dependent are usually infrastructure or network related. Include the approximate time (with timezone) when you submit a report — it helps us correlate your experience with our internal metrics.