I have registered a CDT with @version columns available.
When updating this CDT with OptimisticLockException using the Write To Data Store Entity Smart Service, the status of the Smart Service becomes "not attended" and the process stops.
Are you aware of a technique for handling an exclusive lock as an error when it is detected by Smart Service?
Discussion posts and replies are publicly visible
This is how Appian handles that situation. How exactly would you want to handle that?