Your flow cannot be found. Flow sys_id:nIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } On opening a flow in flow designer, it shows a popup that says " Content not found. Your flow cannot be found. Flow sys_id:n ". Usually observed when a flow is exported between instances Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any release Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } There are two scenarios for this error Scenario 1: The flow cannot be seen in the background behind the popup Scenario 2: The flow can be seen in the background behind the popup For scenario 1: Check if there are any decision tables in the flow on the instance where the flow was exported from. Verify if these decision tables are present in the target instance by sys_id. If not present, import the decision tables using update set and the flow will open without error. If no decision tables are present in both the flow: 1. Take a copy of the affected flow in the affected instance. 2. Go to sys_hub_flow_component table and filter by the flow name 3. Delete actions by grouping them based on type (ex: make a decision, Custom spoke etc) and delete them. Refresh the flow after each batch delete and see if it opens. Note: keep a track of the order field of deleted actions. 4. Once the corrupted action is deleted the flow will open. Repeat the same within the deleted actions to narrow down the corrupted action type and compare with the flow in working instance. For scenario 2: 1. Delete the 'Content cannot be found' popup from the UI. (Right Click - Inspect - Go to Elements - find '<div class="ReactModalPortal"> ' and delete. This will remove the pop - up of 'Content cannot be found Your flow cannot be found. Flow sys_id:n'. 2. Go to 'sources' tab, Hit 'Command + P', Type 'Designer Bundle', choose the first file. 3. Control F and search 'actionsMap[id].warnings' and put a break point at this line 4. Now refresh the flow page again 5. Go to console, search 'warningforinput'and select the file and hit enter 6. This will give the step at which the error is (gives the unavailable/wrongly used catalog variable) - this says that there is an issue with this catalog variable (it can be a data - pill or inline script as well) 7. Keep on hitting on play button so that the next errored catalog variable is seen. 8. Go to catalog item from where this catalog variable is coming from and check if this is available and active.