Monitoring and reprocessing sample limit batch jobs
Key Takeaway
When a sample limit batch job fails, find out why in the batch job and batch job part records. Then reprocess the failed records from the Developer Console by calling the sample limits job service with the action and record IDs that match the trigger handler that failed.
Sample limits cap the quantity of product samples each healthcare account can receive. Life Sciences Cloud creates and updates sample limit records through batch jobs that trigger handlers start, so it can process large volumes of records automatically. When one of these batch jobs fails, a consultant reviews the batch job records to find out why. The consultant then reprocesses the failed records so the sample limits are created or updated.
How sample limit batch jobs work
Sample limit batch jobs create provider sample limit records for each combination of account, product, and assigned sample limit template.
You can monitor and reprocess the batch jobs from three trigger handlers:
CalculateShippedQuantityHandlerNewAccountSampleLimitInitHandlerNewAccountSampleLimitInitHandlerforHCO
When a batch job fails, some sample limits are not created or updated, and they stay that way until you reprocess the failed records.