Queued Transactions Issue

Issue:
The client reported that even though the parallel count was set to 10, only 4 transactions were running, and the rest were stuck in the queue.

More than 1000 transactions were waiting in the queue. Only 2 transactions(whose Trigger in sequence is False) were running.

Error Log (Excerpt):
Event","message":"category="Event" eventId="1376923441239851008"
eventName="CostcoFiscalYear" eventType="DatabaseEvent" groupId="Group_1"
message="Cannot invoke "com.adeptia.indigo.security.IndigoUser.getPassword()"
because "wsUser" is null: Error while creating user subject."[Group Id=192168001075148181566048300002] [User id=1351228373592707072] ...

Issue Explanation:
Transactions were initially activated by an IT user who was later deleted from the system. When we attempted to deactivate and reactivate the transactions using an existing IT user, the process did not work as expected. Since multiple flows were configured with Trigger in sequence, their corresponding entries remained in the ac_sequence_execution_info table under the deleted user ID.
 As a result, the newly triggered instances of these transactions were getting stuck in the Queue.

Fix Applied:
We resolved the issue by clearing the entries from the ac_sequence_execution_info table.
After this, the execution worked as expected for all the transactions.