Hi all,
I’m running into an issue with the Billing Batch Scheduler / Billing Schedule processing.
I have a record-triggered Flow on Billing Schedule for After Insert and After Update. From the flow, I am performing the required DML through an asynchronous/scheduled path approximately 5 minutes after the record transaction
, rather than performing the update immediately in the same transaction. I have automation in Invoice and Invoice Line in a flow in before and after save both.
When the billing batch runs, multiple records are failing and I see the following errors under Revenue Transaction Error Logs
:
I’m also seeing:
There are multiple Revenue Transaction Error Log records with the same/similar errors.
Has anyone encountered the attempt to save object not in TransactionEntityObjectMap error before?
I’m trying to understand:
- What exactly does TransactionEntityObjectMap refer to in Salesforce Billing / Revenue Cloud processing?
- Even though my DML runs asynchronously around 5 minutes later, could it still conflict with Billing Batch Scheduler processing?
- Could the Billing Schedule or related records still be locked or considered part of an active Revenue transaction when the asynchronous flow runs?
- Is there a recommended delay or automation pattern for updating Billing Schedule/related records after billing processing?
- Is this likely a Salesforce internal transaction-state issue, or is there something specific I should avoid updating from the flow?
- Has anyone found a workaround or resolution for this error?
Any insight into the exact root cause of this error and the recommended resolution would be greatly appreciated.
Thanks!