Skip to main content
Solved

PXTransactionScope : Transaction not rolled back


Forum|alt.badge.img

Hi Team,

Not sure if anyone has come across this issue before. We have an Automation schedule that generates invoices. Few days back we had quite a lot of invoices to be generated. When we checked the status of the schedule, we could see many of them were processed successfully, but some of them failed. In the logs we could see the following error for the failed ones “The transaction associated with this command is not the connection's active transaction; see https://fl.vu/mysql-trans”. On further analysis we could see the Invoice did get generated, but Invoices never got linked to their respective Contracts. Ideally the schedule generates the Invoice and links it to the respective Contract , but in this case the Invoices with errors never got linked to the Contract.

Functionality is defined within a transaction scope so not sure why first section of the function worked (generating invoices) , but not the 2nd section (linking the Invoice to a Contract) for some reason didn’t get through.

 

Any thoughts?

 

Best answer by vib1980

It was issue with Acumatica, when the automation schedules overlapped,  in case of a failure/error inner transaction were not getting rolled back. Acumatica provided a hot fix and we have applied this in our prod env.

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img
  • Author
  • 75 replies
  • April 4, 2024

Entire transaction should rollback in case of any error/timeouts.


Forum|alt.badge.img
  • Author
  • 75 replies
  • Answer
  • May 2, 2024

It was issue with Acumatica, when the automation schedules overlapped,  in case of a failure/error inner transaction were not getting rolled back. Acumatica provided a hot fix and we have applied this in our prod env.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2771 replies
  • May 2, 2024

Thank you for sharing the solution with the community @vibindas!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings