What are all possible situations or mistakes in Appian coding, design or modelling can cause deadlock whether it's DB deadlock or any deadlock situation in Appian objects like process model?
Discussion posts and replies are publicly visible
Few Scenario's I would like to share for DB deadlock:
1. When multiple transactions are executing simultaneously and trying to access the same resources in a different order, deadlocks can occur.
2. Long-running transactions can increase the chances of a deadlock, especially if they hold locks on resources for extended periods.
3. If a transaction holds exclusive locks on certain resources and tries to acquire additional locks while other transactions are holding locks on the same resources, a deadlock can happen.
Few Deadlock Scenarios in Appian process model object:
1.Suppose if there is a process model with parallel approval tasks that require different users to review and approve the same document simultaneously. If two or more users try to approve the document at the same time, they might end up in a deadlock situation where each user is waiting for the other to complete their task first.
2.f two processes attempt to update the same field in a database table simultaneously, they might lock each other out, leading to a deadlock.