Monitoring packaged batch and integration jobs
Key Takeaway
Packaged batch jobs run silently, so watch them on the Apex Jobs pages in Setup. When a sample limit handler job fails, read its batch job and batch job part records, then reprocess the failed records with Apex in the Developer Console's Execute Anonymous window.
Agentforce Life Sciences for Customer Engagement includes packaged Apex batch jobs that process large volumes of records in the background, such as product data and sample limits. A consultant runs or schedules these jobs from the Life Sciences Commercial Admin Console. You track their progress and failures on the standard Salesforce Apex job pages. For sample limit jobs, dedicated batch job records also track progress and failures. Because the jobs run silently in the background, you need to know where to look to catch and fix failures.
How to run a packaged batch job
To run batch jobs from the Admin Console, you need the "Life Sciences Commercial Admin" permission set.
Each Admin Console job has two modes. "Run Now" executes the job immediately for a territory and its subordinates, which you select from the appropriate level in the territory hierarchy. "Schedule" runs the job later at a frequency you choose. In both modes, you set the batch size with a slider that defaults to 200.
- Open the App Launcher and select "Life Sciences Commercial".
- Select "Admin Console".
- Pick a tile, for example, "Products", and find the job.
- Choose Run Now and select the territory, or choose Schedule and pick the frequency.
- Use the slider to set the batch size.