Skip to main content

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

: 

 

Revenue Transaction Error during Billing Batch Scheduler – INVOICE_GENERATION_FAILED / UNKNOWN_EXCEPTION

 

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:

  1. What exactly does TransactionEntityObjectMap refer to in Salesforce Billing / Revenue Cloud processing?
  2. Even though my DML runs asynchronously around 5 minutes later, could it still conflict with Billing Batch Scheduler processing?
  3. Could the Billing Schedule or related records still be locked or considered part of an active Revenue transaction when the asynchronous flow runs?
  4. Is there a recommended delay or automation pattern for updating Billing Schedule/related records after billing processing?
  5. Is this likely a Salesforce internal transaction-state issue, or is there something specific I should avoid updating from the flow?
  6. 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!

0/9000