nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

We seem to have one operation interrupting another due to higher priority

jbs_

Hello, We just experienced a situation where one operation was started to delete some documents from our system, and was apparently interrupted by another operation and was suspended. However, when the first operation resumed, it passed the transaction timeout period and was terminated, apparently without a proper rollback. Has anyone else experienced this?

Find more posts tagged with

Comments

jbs_

An update. We have confirmed that the rollback did happen properly. However, the thread executing the operation was suspended, and then resumed just prior to the operation's transaction timeout happened.

Benjamin_Jalon1

If you are on Nuxeo 5.6 can you look during the execution in Admin Center > Activity >Background work...You will have all listeners executed audit and status (in progress, completed, ...)