Catalog Item requests missing workflow context after cloneIssue Catalog Item [sc_req_item] records are missing Workflow Contexts after cloning. Active Catalog Item requests are disconnected from their workflows. As the result of either a clone or upgrade, active RITMs and SCTASKs don't know where they are at in the workflow process. When a SCTASK is marked Closed, it has no effect on the RITM or REQ, so they do not close as they should. The RITM and SCTASK shows no Workflow Context.All newly created Catalog Item requests function correctly and have no workflow issues. This only seems to effect active Catalog Item requests that were replicated from PROD with the clone.FactsThe relationship for Request Management is typically REQ > RITM > SCTASK. When an SCTASK is marked Closed Complete, this cascades backwards to close the RITM and then the REQ.ReleaseAllCauseThis is expected behavior and by default, Workflow Contexts are not copied over in a clone.ResolutionTo clone Workflow Context: Remove the Workflow Context entry from System Clone > Exclude Tables.Clone down instance again.Related LinksExclude a table from cloning