Skip to main content
Rate limits protect both your workspace and the downstream services your workflows talk to. fsckmsft enforces limits at three levels: how many workflow runs can start per minute, how many actions a single run can execute, and how many outbound API calls your workspace can make per minute. Knowing where your plan stands — and what to do when you approach those ceilings — keeps your automations running smoothly.

​
Plan limits at a glance

PlanWorkflow runs / minActions / runAPI calls / min
Free102060
Pro100100600
Business1,0005006,000
  • Workflow runs / min — the maximum number of individual workflow runs that can start within any 60-second sliding window, across all workflows in your workspace.
  • Actions / run — the maximum number of steps a single workflow run can execute, including branches and loop iterations.
  • API calls / min — the maximum number of outbound HTTP requests (webhooks, third-party integrations, the fsckmsft API) your workspace can make per minute.
Limits are enforced at the workspace level, not per individual workflow. A workspace running five active workflows shares one combined quota.

​
View your current usage

Monitor live and historical usage in the Automation dashboard:
  1. Go to Automation → Dashboard.
  2. Open the Usage tab.
  3. Review the three gauges — Runs / min, Actions / run (peak), and API calls / min — each showing current usage against your plan limit.
  4. Use the Time Range picker to view historical usage over the last hour, 24 hours, or 7 days.
A usage spike that reaches 80% of your limit triggers an in-app warning banner. At 95%, fsckmsft sends an email alert to workspace admins.

​
What happens when you hit a limit

When your workspace exceeds the runs-per-minute limit, new runs are placed in a queue rather than dropped. Queued runs execute as soon as capacity is available within the current minute’s window. Runs wait in the queue for up to 10 minutes; if a run has not started within that window, it is dropped and logged as rate_limit_dropped in the Error Log.
Time-sensitive workflows — such as those that send real-time alerts — may deliver delayed or outdated notifications when queued during a rate-limit event. Consider redesigning high-frequency workflows to batch events or use higher-tier plans if delay is unacceptable.

​
Request a limit increase

If your use case legitimately requires higher limits than the Business plan provides, contact fsckmsft support to discuss a custom quota.
1
Open a support request
2
Go to Settings → Support and click New Request.
3
Select the request type
4
Choose Quota / Rate Limit Increase from the category dropdown.
5
Describe your use case
6
Include:
7
  • Your current plan and workspace ID.
  • Which limit you’re hitting (runs/min, actions/run, or API calls/min).
  • Your expected peak usage and a brief description of the workflow architecture.
    • 8
    Await confirmation
    9
    The fsckmsft team typically responds within one business day. Custom limits are provisioned at the workspace level and take effect immediately once confirmed.
    Before requesting a limit increase, review the Automation Dashboard → Workflows list sorted by Runs (last hour). High-frequency workflows are often candidates for optimization — for example, consolidating multiple single-record triggers into a single batch trigger — which can reduce your run count significantly without a plan change.

    ​
    FAQ

    Yes. Every run attempt — including automatic retries configured by a retry policy and manual retries from the Error Log — counts as one run against your quota.
    Yes. Each iteration of a Loop step counts as one action toward the actions-per-run limit. A loop that iterates 50 times over a list of items counts as 50 actions, plus one for the Loop step itself.
    Staging and production workspaces have separate, independent quotas. Rate limits in your staging workspace do not affect production.