https://community.appian.com/discussions/f/data/11667/optimistic-lockingWe are trying to follow best schema practices by referring to the document at https://docs.appian.com/suite/help/17.3/Database_Schema_Best_Practices.html . The main question belongs to the section of &quot;Optimistic Locking&quot; wherein the implementation refersen-USTelligent Community 12https://community.appian.com/thread/51431?ContentTypeID=1Mon, 08 Jan 2018 13:05:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:105aa8e2-4d67-4e18-948c-edc1066572ffAmit MishraDesign a parallel path before the race condition control with timer node and happy path should be ended with terminate node. If collision occurs (process break), then timer node will execute and you can handle it in your way like a task or email notification. If no data collision then terminate node will abort the parallel path. Thanks.<div style="clear:both;"></div>https://community.appian.com/thread/51390?ContentTypeID=1Fri, 05 Jan 2018 18:00:19 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:910e6910-19cd-4c10-b16a-8ae1d704396asudhakaraa0001Thanks for your reply. If you do not mind, could you give me some level of implementation detail for gracefully ending the process? I will pass this by to my developers but still would like to have input from people that might have already implemented this approach.<div style="clear:both;"></div>https://community.appian.com/thread/51389?ContentTypeID=1Fri, 05 Jan 2018 17:46:44 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:aedc5c89-b266-4c3c-9d86-d91511ac0c58Dastagiri DudekulaIn optimistic locking, it pass by exception. Here System administrator has to manually intervene. Try using any flag or timer by defining the parallel flow before the db operation node<div style="clear:both;"></div>