Scheduled Job Health Monitoring

Overview

Scheduled Job Health Monitoring tracks every scheduled Apex job and recurring batch process in your org. When a submitted-by user goes inactive, or when a job fails three times in a row, OrgGuard creates a finding and routes the alert per the originating policy’s notification settings — before the failure causes a silent data or integration outage.

Who this page is for

Salesforce admins and platform engineers who own integration reliability and scheduled job governance. If you’ve ever inherited a scheduled Apex job submitted by a former employee — or discovered a failed batch only after a downstream report went wrong — this module is for you.

Scheduled jobs in Salesforce run under the security context of the user who submitted them. If that user is deactivated, frozen, or deleted, the job continues to run but processes no data — and Salesforce surfaces no warning. OrgGuard detects this condition on every scan and raises a finding, routing the alert per the originating policy’s notification settings before damage accumulates.

---

What you’ll see

The Scheduled Job Health experience is two screens:

• Scheduled Job Inventory — a dashboard and list view of every discovered scheduled job with health metrics, owner status, next fire time, last fire status, and consecutive failure count
• Finding detail — the standard OrgGuard findings view, with job-specific context on why the finding was created

Dashboard metrics

The top of the Scheduled Job Inventory shows four metrics cards:

Card	Description
Total Jobs	Count of all scheduled jobs discovered in your org
Active	Jobs whose JobStatus__c is Active
Failing	Jobs that have exceeded the consecutive failure threshold
Error State	Jobs whose JobStatus__c is Error (e.g., missing class)

Job list view

Below the metrics, a list shows one row per job with columns for:

Column	Description
Job Name	The name of the scheduled Apex class, Flow, or batch job
Status	The job’s JobStatus__c: Active, Paused, Error, or Deleted
Apex Class	The fully qualified Apex class name being scheduled
Schedule	The cron expression defining when the job runs
Next Run	When the job is next scheduled to fire
Last Run	The timestamp of the most recent execution
Failures	Consecutive failure count since the last successful run
Owner	The submitted-by user who owns the job’s run context

The list has two separate filters: a Status filter (All / Active / Paused / Error / Deleted) and a Failing/Healthy failure filter. A job with consecutive failures over the threshold shows in the Failing failure filter and means OrgGuard has created or will create a finding on the next scan. “Inactive Owner” is a finding type, not a status — find those in the Findings tab.

Screenshot pending

Screenshots will be added when the Scheduled Job Inventory LWC ships.

---

How OrgGuard detects job health problems

OrgGuard runs scheduled job discovery as part of every org scan. It queries CronTrigger and AsyncApexJob to build the inventory, then checks two conditions:

Condition 1 — Inactive submitted-by user If the user who submitted a job (CronTrigger.CreatedById) is inactive, frozen, deleted, or locked, OrgGuard creates an Inactive Owner finding for the job. The job may still execute, but it runs in a degraded context with no user to receive failure notifications.

Condition 2 — Consecutive failures If a job’s last N executions all have a status of Failed (where N is configurable, default 3), OrgGuard creates a Consecutive Failure finding. A single failure may be transient; three in a row is a pattern.

Both finding types route according to the originating policy’s notification settings (the Inactive Job Owner and Job Failure Threshold policies). When Notify Asset Owner is on, alerts go to the job’s submitted-by user; when Notify Admin Group is on (or when there is no usable owner), alerts go to the admin group. Scheduled jobs have no OrgGuard owner-override.

Detection cadence

Scheduled-job failure counting runs once per day, when the OrgGuard SJH Daily Poll flow fires at 6 AM. Each daily check counts the most recent run, so a persistently-failing job reaches the consecutive-failure threshold (default 3) after roughly three daily checks. Hourly detection is planned as a future enhancement.

---

Common tasks

View all jobs with health problems

Who can do this: OrgGuard Admin, OrgGuard User, OrgGuard Auditor

Prerequisites: At least one scan has run since Scheduled Job Health Monitoring was enabled.

1. Open the OrgGuard Lightning app and click Scheduled Jobs in the navigation.
2. Set the Failing/Healthy failure filter to Failing to surface jobs over the consecutive-failure threshold. Use the Status filter (Active / Paused / Error / Deleted) to narrow further — e.g. Error for jobs in a Salesforce error state.
3. Review the filtered list. Jobs in the Failing filter need investigation into why the Apex class or batch is erroring. To find jobs whose submitted-by user has gone inactive, open the Findings tab and look for Inactive Owner findings.

Expected result: A filtered list of jobs requiring attention. If the list is empty, all discovered jobs are within the failure threshold.

---

Open a scheduled job’s record

Who can do this: OrgGuard Admin, OrgGuard User, OrgGuard Auditor

Prerequisites: The job appears in the Scheduled Job Inventory.

1. In the job list, open the row’s action menu and click View.
2. OrgGuard navigates to the job’s standard Salesforce record page, where you can review its schedule, status, submitted-by user, and failure history.

Caution

Scheduled jobs do not have a custom OrgGuard ownership panel or an Override owner button — that owner-override workflow is certificate-only. A scheduled job’s owner is its native Salesforce submitted-by user (CronTrigger.CreatedById), which OrgGuard reads but does not change. To change who Salesforce runs a job as, you must abort and reschedule it under the correct user — see the remediation task below.

---

Remediate a job with an inactive submitted-by user

Who can do this: OrgGuard Admin (requires Apex execution permissions in Salesforce)

Prerequisites: The job has an Inactive Owner finding in OrgGuard. The new user is active and has the required permissions to run the job’s Apex class.

Salesforce does not allow updating the submitted-by user on a running job. Remediation requires aborting the job and rescheduling it under the correct user.

Steps:

1. From the Scheduled Job Inventory, note the Job ID and the Apex class name (shown in the job detail view).
2. Open the Salesforce Developer Console or Execute Anonymous window.
3. Abort the existing job:

   System.abortJob('YOUR_CRONJOB_ID');

4. Reschedule the job under an active user context. For a daily 2 AM schedule:

   String jobId = System.schedule(
     'Your Job Name',
     '0 0 2 * * ?',
     new YourSchedulableClass()
   );

5. Return to OrgGuard, trigger a manual scan, and confirm the job inventory shows the new submitted-by user as active.
6. Resolve the finding manually or wait for the next scan to auto-resolve it.

Expected result: The rescheduled job appears in the inventory with an active submitted-by user. The Inactive Owner finding is resolved.

Caution

Rescheduling under the wrong user or a user without the right permissions will cause the job to fail immediately. Verify the new user has the same permission set as the previous owner before rescheduling.

---

Acknowledge a consecutive failure alert

Who can do this: OrgGuard Admin, OrgGuard User

Prerequisites: A Consecutive Failure finding exists for the job.

1. Open the Findings tab. Search for the job name to locate its finding. (Known gap: there is no dedicated Scheduled Job finding-type filter — locate the finding by searching for the job name.)
2. Review the failure count and the last error message (if available from AsyncApexJob).
3. Click Acknowledge and add a resolution note describing the investigation status.
4. Resolve the underlying Apex error in the class, then trigger a manual scan.

Expected result: Once the job executes successfully, OrgGuard auto-resolves the finding on the next scan. The consecutive failure count resets to zero.

---

Failure threshold reference

Setting	Default	Notes
Consecutive failure threshold	3	Configurable per policy
Alert deduplication window	24 hours	Same as CLM alerts
Owner routing	Per the policy’s Step-4 toggles: submitted-by user (Notify Asset Owner) and/or admin group	Same notification engine as Certificate Lifecycle Management

---

Troubleshooting

Symptom	Likely cause	Fix
A scheduled job I know exists is not in the inventory	Discovery has not run since the module was enabled, or the job was created after the last scan	Trigger a manual scan from Scan Management
Finding created but the submitted-by user is still active	The user was deactivated between the job being submitted and the last scan	OrgGuard detected the deactivation on the most recent scan — the finding is correct
Job keeps failing after I rescheduled it	The new user lacks required permissions, or the Apex class has a code-level bug	Check the AsyncApexJob error log in Salesforce; review the class’s required permission sets
Findings not routing to the right person	The originating policy’s notification toggles don’t match where you expect alerts	Edit the Inactive Job Owner / Job Failure Threshold policy’s Step 4 — enable Notify Asset Owner and/or Notify Admin Group and set the Admin Group Email
I aborted the job but OrgGuard still shows it	Aborted jobs remain in CronTrigger with status DELETED until the next OrgGuard scan clears them	Trigger a manual scan; the job will be removed from the inventory

---

FAQ

Does OrgGuard abort or reschedule jobs automatically? No. Scheduled job remediation requires human judgement — the new owner must have the correct permissions, and the schedule may need adjusting. OrgGuard provides guided instructions but does not execute Apex on your behalf.

Does OrgGuard monitor all scheduled job types? OrgGuard discovers Apex Class scheduled jobs, Batch Apex, recurring Queueable chains, and Flow schedules that appear in CronTrigger. Jobs that run entirely via Platform Events or external schedulers are not discoverable.

Can I suppress alerts for a job that’s intentionally inactive? Yes — create a Suppression via the finding’s Suppress action. OrgGuard will not alert on that job again unless the suppression expires or is manually removed.

What happens when a job succeeds again after failures? OrgGuard auto-resolves the Consecutive Failure finding on the next scan that detects a successful execution. No manual action is needed.

Will OrgGuard detect newly scheduled jobs automatically? Yes — every scan re-queries CronTrigger and adds newly discovered jobs to the inventory.

---

Related

• Scheduled Jobs — manage OrgGuard scheduled jobs and understand refresh cadence
• Findings — review and triage scheduled job health findings
• Notifications — configure who receives job failure alerts
• Asset Inventory — unified view of all operational assets including scheduled jobs
• Permission Sets — who can view and manage scheduled job health findings