Workflow getting reattached on update of old RITM recordIssue An old RITM record that had no updates in a long time may be observed getting a new workflow attached again, possibly after years of the RITM record inactivity.ReleaseThere is a table clean-up module in charge to delete the inactive workflow contexts, controlled by the scheduled job 'BulkTableCleaner'. The deletion process is specific to the criteria defined in the sys_auto_flush table for a record.CauseAn update to the RITM record has triggered the workflow again, and the context got created correspondingly. This was observed in a use case where the administrator had not defined any condition in 'Workflow Properties' to restrict the workflow to get attached. The workflow properties condition is 'Run the workflow always', which is does not prevent the workflow to get attached again even if it reaches the 'End' activity already.ResolutionThese steps help troubleshooting how the workflow may get attached to a RITM record after the old/earlier context is deleted: Create some catalog requestGo to the workflow context created for the catalog requestDelete the created contextOpen the RITM recordPerform some modification to the RITM recordCheck if the workflow gets attached to the RITM recordCheck the workflow properties