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
I think there is not much difference to any other software development environments. Do you have any specific question?
No, I don't have any specific questions related to deadlock in Appian.
But, I would like to know in which all situations (Bad Practices/Coding done by Developer) Appian reports a deadlock situation.
Like one can have a deadlock situation when working with data with MNI. What are the possible bad practices if done then it can cause a deadlock in Appian?
Appreciate it!
This is too broad a question IMO. To avoid a deadlock, you simply have to avoid doing many concurrent writes to a table. Not sure what else to suggest.
The only situation I can remember that I would call a deadlock was, that I built two processes waiting for each other.
Not sure what you have in mind.
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.
This can eventually lead to a condition called "starvation," where there are no resources available for use by any process Mapquest