[LS-914] SRD Request 2201 Created: 03/Feb/26  Updated: 15/Apr/26  Due: 06/Feb/26

Status: Ready for QA
Project: L3 Support
Component/s: SRD
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Abir Messaikeh Assignee: Abir Messaikeh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 4 hours
Original Estimate: Not Specified

Attachments: XML File SRD_MAIN.bpmn20.xml    
Customer:
OMAN-Tel
Planned Start:
Planned End:
Product: NEP
Actual Start:
Date of Baselining:

 Description   

Dear support, Kinly check why solution not highlighted in request 2201



 Comments   
Comment by Abir Messaikeh [ 03/Feb/26 ]

as workaround we asked the user to make a start over

Comment by Ayed Bada [ 03/Feb/26 ]

During execution of the SRD process (attached BPMN), i observed the following error:
ORA-00001: unique constraint (SRD_PROD.SYS_C0063096) violated
Root Cause:
This issue occurs in the parallel multi-instance call activity due to a concurrency conflict when Flowable tries to insert multiple activity instances into the database at the same time.
The problem is intermittent and does not happen on every execution.
Under high traffic or simultaneous execution, multiple parallel instances may attempt to insert the same activity instance ID, triggering the unique constraint violation.
When the process is restarted (“Start over”), it usually completes successfully because the timing of the parallel inserts differs, avoiding the collision.
Solution:
Remove flowable:completeAsync="true" from the call activity to prevent the activity scope from being completed asynchronously.
This ensures the multi-instance inserts happen within the same transaction context, eliminating the race condition.

Comment by Abir Messaikeh [ 15/Apr/26 ]

pending stress test or further tests for variable on staging b4 apply new process on PROD

Generated at Wed Apr 15 15:54:55 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.