Workflow activity creates a conflicts when Async Job is triggered with current.update();Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Some of the symptoms are: - The value of the state field is different on Form and Audit history - The value of the state field was not set as expected according to the workflow activity- This issue is intermittent Release All versions Cause When the workflow is setting the value of the state, at the same time an Async Job runs which is updating the record.- The following functions can cause the discrepancy and lead to inconsistent results "autoSysFields(false)","setWorkflow(false)""current.update()" Recommendation - We do not recommend to have an ASYNC processing when there is a Workflow attached to a Task Record.