Watch Salesforce org limits with Platform Limits Health
Track Salesforce org limits such as API calls and storage over time, see which are critical or trending to exhaustion, compare orgs, and get a daily digest email when a limit is at risk.
Overview
Platform Limits Health watches the org-wide limits Salesforce enforces — daily API requests, data and file storage, async Apex executions, and many more — and warns you before one runs out.
Readings are collected automatically at the end of each org sync, and you can collect on demand. Readings are kept for 10 days, which is enough to see trends and estimate when a limit will be reached.
Each limit gets a risk level:
| Risk | When |
|---|---|
| Critical | 5% or less remaining |
| High | 85% or more used and rising, or an abnormal spike |
| Moderate | 85% or more used; or projected to hit the threshold within 3 days; or 70% or more used and rising |
| Low | Everything else |
The org's health score starts at 100 and loses 40 points per critical limit, 20 per high and 7 per moderate. When you compare orgs, the portfolio score is the worst org's score.
Before you start
- Connect the org. Readings need a working Salesforce connection.
- Scheduled syncs keep readings flowing without anyone pressing a button.
Steps
- Open Platform Limits Health under Monitoring, Runtime & Logs and pick the org.
- If there is no data yet, click Collect now. To refresh every org at once, click Collect all orgs — it runs in the background and you can Cancel it.
- Read the tiles: Health score, Critical, Approaching threshold, Abnormal consumption, Trending to exhaustion and Limits tracked.
- Scan the matrix (Limit, Used, Remaining, Capacity, Trend, Risk). Click a column header to sort.
- Click a limit to open its detail. Switch the window between 24 Hours, 3 Days, 7 Days and 10 Days.
- Read Estimated time to threshold, then the sections What we observed, Likely cause, Business impact, Recommended next steps, Recovery and Evidence.
- Switch the mode from This org to Compare orgs (N) to see all orgs side by side.
Example
Priya, a release manager, gets a daily digest for acme-prod: daily API requests are at 88% and rising. She opens the limit detail, sets the window to 3 Days, and sees usage jumped after a new integration went live. Estimated time to threshold says about 9 hours. She asks the integration team to batch their calls before the limit is hit.
FAQs
Who gets alert emails?
Alerts go out only for critical and high risks, as one daily digest email per org ("Platform Limits · Daily digest", subject starting "[ACTION REQUIRED]"). Recipients are set in Communication Center under "Salesforce limit at risk" — by default, the workspace admins.
Will I be emailed about the same limit every hour?
No. A limit is re-sent only when it is new, has escalated, has moved by 10 points or more, or 24 hours have passed.
Why do I see "One reading so far"?
Collection succeeded, but a trend line needs at least two readings. It fills in after the next collection or sync.
Troubleshooting
"No platform limit data yet"
Run a sync, or click Collect now once the org is connected.
Compare orgs is empty
Comparison needs at least one org with collected readings. Use Collect now on an org first.
Collection fails for one org
The org's credentials may have expired. Reconnect it from Connections, then collect again.
Related articles
Was this article helpful?
Related articles
- Manage emails in the Communication CenterSee every email MetaLens360 sends for your workspace, switch alerts on or off, preview and test them, customize the subject, content and recipients, and review delivery activity.
- Schedule automatic syncsCreate sync schedules in Settings so your orgs refresh on their own — choose a time, days, sync mode, how many orgs sync at once and the order they run in.
- Investigate async Apex failures with Runtime ForensicsPull failed batch, queueable, future and scheduled Apex jobs from an org, grouped by root cause, with a daily trend, the classes involved and where to look for each cause.
- Fix expired org credentialsWhen an org shows Reconnect needed, Salesforce has refused its stored credentials. Re-credential it in place from the Edit dialog without losing any synced data.