Skip to main content
Question

Issue When Multiple BPA Workflows Update the Same Record

  • November 24, 2025
  • 6 replies
  • 57 views

Forum|alt.badge.img+3

Hi All,

 

I am facing an issue in the BPA Workflows. I have created 3 different Asynchronous workflows, and each one has its own logic. All the three workflow triggered when a record is inserted into the ‘JtTask’ entity using Custom event.

For an Example, each workflow updates a different field in the ‘JtTask’ entity:

Workflow 1 → Updating Task description field value.

Workflow 2 → updating Custom field value.

Workflow 3 → updating the Priority field value.

 

Most of the time, all three workflows run correctly and all fields get updated.

But sometimes, only two fields get updated and one field does not update. When I troubleshoot the workflow that didn’t update the field, it shows no error — the workflow completes successfully during troubleshooting.

 

Is this happening because all three workflows have the same trigger point and are trying to update the same record at the same time, causing version issues?  Or What could be the cause of this problem?

How should we handle this type of situation in BPA Workflows?

 

Thanks in Advance!

Sandya S

6 replies

Forum|alt.badge.img+9
  • Hero (Employee)
  • November 24, 2025

Hi ​@SNG_SS ,

There is a possibility of errors occurring if we update the same record with multiple workflows at the same time.

In cases where a workflow fails, does any error appear in the error log within the async sys table?

With async workflows, if one fails, it will automatically retry after a while, which may resolve the issue.

I’m interested to know if there’s a specific reason for using three workflows to perform the update this way?


Forum|alt.badge.img+3
  • Author
  • Sidekick (Partner)
  • November 25, 2025

Hi,

yes, I got the ‘RuntimeException--Resource not found’ error in the log. And I am using the ‘TaskSeq’ as a workflow input from the custom event. 

For each field update, i need to do some data manipulation logic and based on some condition I am updating the field. That’s why I have created the different workflows to reduce the complexity of it. 

Even If i combine the logic in single workflow to update all the fields, I am worried that, if any one update fails, then all other updates might also fail. Is there any other efficient way to update the fields for such scenarios?


Forum|alt.badge.img+9
  • Hero (Employee)
  • November 25, 2025

hi ​@SNG_SS ,

Receiving a 'resource not found' error, even though it works when you run troubleshoot later, suggests that the entry might not be available during the workflow execution at that specific time.

There's also a chance the 'resource not found' error comes from reading another entity in the workflow, rather than the jttask read itself, possibly due to a race condition with data creation.

If you aren't already, it's a good practice to read the entity before making any updates to avoid version issues.

Is the workflow that's failing always the same one, or does it happen randomly?


Forum|alt.badge.img+3
  • Author
  • Sidekick (Partner)
  • November 25, 2025

Hi,

Yes, Its happening randomly.


Forum|alt.badge.img+9
  • Hero (Employee)
  • November 25, 2025

hi,

Is there a possibility to share the workflows so we can take a look and see ?

Alternatively, If possible, you could log a support case for this to analyze further 


Forum|alt.badge.img+3
  • Author
  • Sidekick (Partner)
  • November 27, 2025

Hi ​@kamnlk 

Thanks for your support! I found the cause of the issue. The error occurred because in the workflow I am trying to read another entity data,  but if the user doesn’t have access to that record—for example, if they don’t have access to the site—it throws a "resource not found" error. So its because of the data access issue.