In this article, we explore key Salesforce objects related to scheduled jobs and shed light on some commonly misunderstood job types like Report Run, Reporting Notification, and Sitemap SEO Generation Job — all of which require attention during user deactivation.
When deactivating a user in Salesforce, it’s easy to think of it as a simple toggle — but the reality is far more complex. Users often own critical business records, are part of automation flows, or have scheduled jobs tied to their identity. Failing to review these associations can lead to system disruptions or silent failures
Key Objects Involved in Scheduled Jobs
1. CronTrigger
The CronTrigger object represents the schedule of a job, holding details like:
- Cron expression
- Next fire time
- Start time
- End time
- State (Active/Complete/Deleted)
Use this object to understand when a job is scheduled to run.
2. AsyncApexJob
The AsyncApexJob object represents an asynchronous job like:
- Batch Apex
- Queueable
- Future methods
Each job is logged when an Apex class is scheduled and executed when system resources are available.
3. CronJobDetail
This object stores metadata about the job, such as:
- Job name
- Job type
You can link it to CronTrigger using CronTrigger.CronJobDetailId. It’s useful for querying and analyzing scheduled jobs by type.
Job Type Reference Table
| Job Type | Code |
| Data Export | 1 |
| Dashboard Refresh | 3 |
| Reporting Snapshot | 4 |
| Scheduled Flow | 6 |
| Scheduled Apex | 7 |
| Report Run | 8 |
| Batch Job | 9 |
| Reporting Notification | A |
| Sitemap SEO Generation Job | E |
| Sitemap SEO Incremental Job | G |
| Autonomous Data Loader Job | K |
Report Type Metadata for Search | T |
| Standard Report Metadata | X |
Understanding Job Types
Report Run
If you notice a scheduled job with the name Report Run, it indicates that a user has scheduled a report.
If that user is about to be deactivated, you’ll need to reschedule the report under another active user to ensure continued delivery.
Reporting Notification
This job appears when a user has subscribed to reports or dashboards.
The number of jobs here depends on how many subscriptions the user has. If you deactivate the user without reassignment, notifications will fail silently.
Sitemap SEO Generation Job & Incremental Job
These jobs are tied to published Experience Cloud sites (communities).
If these jobs are present, it means the user being deactivated was the one who published the site. Deactivating this user without reassigning the publishing role can result in broken sitemap indexing.
How to Resubmit These Jobs:
- Navigate to Setup > Environments > Jobs > Scheduled Jobs.
- Delete existing Sitemap jobs submitted by the deactivating user.
- Login as the new user who will own the site jobs.
- For each Experience Cloud site:
- Go to Setup > Digital Experiences > All Sites
- Open the site in Builder
- Make any small change → Publish the site
- The sitemap jobs will regenerate under the new user.
Conclusion:
By understanding key Salesforce objects like CronTrigger, AsyncApexJob, and CronJobDetail, and properly reassigning or rescheduling these jobs, you can ensure business continuity and avoid silent failures.