RITM : New wf_context created upon record update and new sc_task records generatedDescriptionThere are multiple ways for a wf_context record to be deleted. One method is to use the table cleaner job that clears all inactive wf_context that have ended more than 'n' days ago. However, this is the assumption that parent record is no longer relevant and will no longer be touched. If parent record is then updated, a workflow will reattach and create a new wf_context record.NOTE: any workflow with a matching condition in theory could reattach. Steps to Reproduce 1) Create a workflow on sc_req_item table and add create sc_task activity in the workflow 2)Attach this workflow to sample catalog item and order it 3) RITM (Requested Item) will be generated and will be governed by the workflow attached to it (which will generate a task) 4)Close this task 5)now delete the associated workflow_context record for this RITM and make any update on the RITM 6)A new workflow context will be generated and new sc_task record will be created for this RITM ResolutionFind the record on table wf_context and mark it inactive (active=false). To prevent old records whose contexts have been deleted from reattaching to workflows involves adding a condition to the workflow. Set the workflow condition to execute if Active=true. If there is no Active field on your table you might try using a condition where you only attach workflows if the creation date is within the last 7 days.Additional InformationObservation: 1)There is a table clean up module in ServiceNow which deletes the inactive workflow contexts. 2)The deletion process is specific to the criteria defined in the sys_auto_flush table for a record. 3) The table clean is controlled by a scheduled job 'BulkTableCleaner'. 4)Noticed that an update to the RITM record has triggered the workflow again and context got created correspondingly. 5)Reason for the above finding is, under 'Workflow Properties' the customer did not define any condition to restrict the workflow to get attached. 6)The condition under workflow properties is 'Run the workflow always' which is incorrect if we expect the workflow to not get attached again if it reaches 'End' activity already.