Is Your Salesforce Org Healthy? Stop Guessing with mtdt.io Healthcheck
If you’ve ever managed a Salesforce environment for a long time—or inherited one from a previous consultant—you know the feeling. You start to wonder: How many of these Apex classes are running on ancient API versions? Are our automated flows actually active? Why did that scheduled job fail silently three days ago?
Maintaining a Salesforce org shouldn’t feel like detective work. mtdt.io Healthcheck answers that question directly: it's a centralized monitoring suite that scans your org for inactive flows, outdated Apex API versions, lost users, timezone mismatches, Apex job failure rates, storage utilization, and license expirations — surfacing the issues before they cause an outage or a deployment failure.
At mtdt.io, we believe that "deployment" is only half the battle. Staying "green" day-to-day is where the real work happens. That’s why we built Healthcheck—a centralized monitoring suite designed to give Admins and Devs a clear view of their org’s vital signs.
Healthcheck is an early-warning system: it catches technical debt before it becomes a deployment blocker.
What Does mtdt.io Healthcheck Actually Watch?
We didn’t just pick random metrics. We focused on the "silent killers"—the things that usually go unnoticed until something breaks or a limit is hit.
1. Code & Automation Freshness
- Inactive Flows: It’s easy to lose track of versions during a busy sprint. We flag flows where the latest version isn't the active one, ensuring your logic is up to date.
- Class API Versions (The "Max Lag" Feature): Salesforce moves fast. If the current API version is 62, but your code is stuck on version 45, you’re missing out on performance and security updates.
- Configure Max Lag: In mtdt.io settings, you can define your threshold. For example, if Max Lag is set to 3 and the current version is 62, any class on version 58 or lower gets flagged as Outdated. Anything no longer supported by Salesforce is marked Unsupported.
2. User & Access Security
- Lost Users: We hunt for users who haven't logged in for an extended period. Clearing them out tightens security and recovers license cost.
- Timezone Checks: Did you know that if your Automation User’s timezone doesn't match the Organization’s timezone, your scheduled logic might be firing at 3:00 AM instead of 3:00 PM? We flag these mismatches instantly.
3. Operational Stability
- Apex Job Failure Rates: We don't just tell you a job failed; we monitor the rate of failure so you can spot patterns before they become a crisis.
- Daily Async Executions: Stop hitting the "Apex Limit Exceeded" wall. We watch your async limits and scheduled job counts so you can scale safely.
- Space Utilization: Get ahead of the "Storage Full" notification that stops your users from creating records.
4. Proactive Warnings
- License Expirations: No more "Oops, the Sandbox expired" or "Managed Package X just stopped working." We warn you when licenses are nearing their end.
- Test Stats: Keep an eye on your overall test health and coverage trends without running a manual 4-hour "Run All Tests" cycle.
Why This Changes Your Daily Maintenance
For the "In-House" Admin
Instead of spending Monday morning clicking through Setup menus to check logs, you open mtdt.io. You get a "Coffee-Ready" report of exactly what needs attention. You move from reactive fixing to proactive health management.
For the Consultant / Managed Service Provider
If you manage multiple customer orgs, Healthcheck is your "Peace of Mind" dashboard. You can prove value to your clients by showing them a clean health report every month and catching potential API versioning issues before they turn into technical debt.
Beyond the Basics: The Strategic Advantage
The real payoff of monitoring is Optimization.
- Technical Debt Reduction: By enforcing API versioning and cleaning inactive flows, you keep the metadata lean.
- Cost Savings: Finding "Lost Users" allows you to reclaim expensive licenses immediately.
- Better Audits: When it's time for a security or system audit, you already have the data ready.
FAQ
What does mtdt.io Healthcheck actually monitor? It watches code and automation freshness (inactive flows, outdated Apex API versions), user and access security (inactive users, Automation User timezone mismatches), operational stability (Apex job failure rates, daily async execution limits, storage utilization), and proactive warnings like license expirations and test coverage trends.
How does the "Max Lag" feature work for Apex API versions? You set a Max Lag threshold in mtdt.io settings — for example, if Max Lag is 3 and the current Salesforce API version is 62, any class on version 58 or lower is flagged as Outdated, and any class on a version no longer supported by Salesforce is marked Unsupported.
Can Healthcheck catch scheduled jobs firing at the wrong time? Yes. mtdt.io flags a mismatch between your Automation User's timezone and the organization's timezone, which is a common cause of scheduled logic firing at an unexpected hour.
Does Healthcheck help before licenses or sandboxes expire? Yes. It warns you when licenses are nearing their end, so you avoid surprises like an expired sandbox or a managed package that suddenly stops working.
Who is mtdt.io Healthcheck built for? It's built for in-house admins who want a single report instead of manually checking Setup menus, and for consultants or managed service providers who monitor multiple client orgs and want a repeatable health report to show clients.
Ready to see your org’s vitals?
The mtdt.io Healthcheck is designed to be set up once and trusted forever. Configure your max lag, set your thresholds, and let us do the heavy lifting.
Log in to mtdt.io and run your first Healthcheck today.
Related: Pre-Deployment Checks · Salesforce Static Code Analysis
Was this page helpful?
Let us know how we did