RITM reopens after months of being closedIssue System update the RITMs after months from closed to open state. Impacted RITMs are records with below conditions: a. Have a workflow b. Stage is in 'request_approved' c. Workflow context is empty due to the OOB "Auto flush" on wf_context that removes workflow contexts that ended after 180 days./sys_auto_flush.do?sys_id=552f483c0a0a0b900082121e6ea5b65eCauseThe issue is due to the custom workflow which does not define stages causing the sc_req_item.stage to remain in 'request_approved', allowing the possibility to re-trigger the OOB Business rule "Start Workflow" when conditions are met. Service Catalog uses the business rule "Start Workflow" on table sc_req_item to trigger the workflow execution when field sc_req_item.cat_item has a workflow defined, sc_req_item.stage='request_approved' and sc_req_item.context field is not defined.Resolution1. When using Service Catalog consider to update the sc_req_item.stage field to a different value except "request_approved".In the custom workflow, use the existing activities to define a Stage value to update sc_req_item.stage field - Under the workflow canvas open the form view of any activity like the Set Values ("Open") activity and refer to field "Stage" - On OOB Tokyo refer to workflow "Service Catalog Item Request" as a sample for use of Stages under a sc_req_item workflow Note: this workflow is using "Legacy" stage renderer so consider to use "Workflow-driven" instead 2. If the custom workflow now defines Stages and if any sc_req_item re-opens, then this new workflow execution should be updating the field sc_req_item.stage with a different value except "request_approved" so this workflow also could be used to fix existing affected records.3. Another option is to create a background script to update just the field sc_req_item.stage of existing affected RITM records following the new Stage definition under custom workflow. For this script consider to disable the execution of business rules during the GlideRecord update.WARNING: Before applying any of this in a Production instance, test and validate thoroughly in non-prod instances.