[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-18(UTC)"],[[["\u003cp\u003eThis document provides troubleshooting guidance for the \u003ccode\u003eflow.SharedFlowNotFound\u003c/code\u003e error in Apigee and Apigee hybrid environments, which indicates that a specified shared flow cannot be found.\u003c/p\u003e\n"],["\u003cp\u003eThe error \u003ccode\u003eflow.SharedFlowNotFound\u003c/code\u003e occurs when a shared flow referenced in a Flow Callout policy's \u003ccode\u003e<SharedFlowBundle>\u003c/code\u003e either does not exist or is not deployed in the environment where the API request is executed.\u003c/p\u003e\n"],["\u003cp\u003eTo diagnose this error, check the error response's \u003ccode\u003efaultstring\u003c/code\u003e to identify the missing shared flow, then verify its existence and deployment status within the Apigee UI under the "Shared Flows" section.\u003c/p\u003e\n"],["\u003cp\u003eResolution steps involve either creating and deploying the missing shared flow in the correct environment, or updating the Flow Callout policy to reference an existing, deployed shared flow, ensuring it's deployed in the environment where it is being called.\u003c/p\u003e\n"],["\u003cp\u003eThe document showcases practical examples of the error message, diagnosis steps, and resolution methods, using sample shared flow names and UI screenshots to aid in understanding and rectification.\u003c/p\u003e\n"]]],[],null,["*You're viewing **Apigee** and **Apigee hybrid** documentation.\nView [Apigee Edge](https://docs.apigee.com/api-platform/troubleshoot/policies/runtime/flowcallout-runtime-errors) documentation.*\n| **Note:** Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().\n\nSharedFlowNotFound\n\nError code \n\n flow.SharedFlowNotFound\n\nError response body \n\n```\n{\n \"fault\": {\n \"faultstring\": \"Shared Flow shared_flow_name Not Found\",\n \"detail\": {\n \"errorcode\": \"flow.SharedFlowNotFound\"\n }\n }\n}\n```\n\nPossible Causes\n\nThe possible causes for this error are:\n\n|---------------------------------------------------------------|---------------------------------------------|\n| **Cause** | **Description** |\n| [Shared flow not available](#cause_shared_flow_not_available) | The shared flow does not exist. |\n| [Shared flow not deployed](#cause_shared_flow_not_deployed) | The shared flow exists but is not deployed. |\n\nCause: Shared flow not available\n\nIn the Flow Callout policy, if the shared flow defined within the `\u003cSharedFlowBundle\u003e` element does not exist in the environment, then this error occurs.\n\nFor example, If the `\u003cSharedFlowBundle\u003e` element in the Flow Callout policy contains a shared flow called `SharedFlow_Sample` and if this shared flow does not exist in the environment, then the error occurs.\n\nExample Error Message \n\n {\n \"fault\": {\n \"faultstring\": \"Shared Flow SharedFlow_Sample Not Found\",\n \"detail\": {\n \"errorcode\": \"flow.SharedFlowNotFound\"\n }\n }\n }\n\nDiagnosis\n\n1. Identify the shared flow which does not exist. You can find this in the `faultstring` element of the error response. For example, in the following `faultstring`, the shared flow name is `SharedFlow_Sample`:\n\n `\"faultstring\": \"Shared Flow SharedFlow_Sample Not Found\"`\n2. Examine all the Flow Callout policies in the specific API Proxy where the failure has occurred. Check if there is any Flow Callout policy in which `\u003cSharedFlowBundle\u003e` element is specified with the flow name identified in step #1 above.\n\n For example, the following policy specifies the `\u003cSharedFlowBundle\u003e` as `SharedFlow_Sample`, which matches with what's in the fault string. \n\n \u003cFlowCallout async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"Auth-Flow-Callout\"\u003e\n \u003cDisplayName\u003eAuth Flow Callout\u003c/DisplayName\u003e\n \u003cSharedFlowBundle\u003eSharedFlow_Sample\u003c/SharedFlowBundle\u003e\n \u003c/FlowCallout\u003e\n\n3. In the UI, check if this shared flow exists under **Develop \\\u003e Shared Flows**. If it does not exist, then that's the cause of the error. (Note that in the New UI, you can find Shared Flows under the Develop tab.)\n\n For example, in the screenshot shown below, the shared flow `SharedFlow_Sample` does not exist.\n\n Because this shared flow does not exist, you receive the error code: \n\n flow.SharedFlowNotFound\n\nResolution\n\nEnsure that the shared flow specified in the `\u003cSharedFlowBundle\u003e` element in the Flow Callout policy, exists and deployed in the specific environment in which the API request is executed.\n\nYou could choose one of the following ways to address the issue:\n\n1. Create a shared flow called `SharedFlow_Sample` and deploy it the test environment as shown below:\n\n2. Use an already existing Shared Flow that is deployed in the test environment in the Flow Callout policy. For example, you could specify **SharedFlow_demo** in the Flow Callout policy.\n\n \u003cFlowCallout async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"Auth-Flow-Callout\"\u003e\n \u003cDisplayName\u003eAuth Flow Callout\u003c/DisplayName\u003e\n \u003cSharedFlowBundle\u003eSharedFlow_demo\u003c/SharedFlowBundle\u003e\n \u003c/FlowCallout\u003e\n\n If you make an API call to the test environment, you will no longer see the\n error, because the Flow Callout is deployed to the test environment as well.\n\nCause: Shared flow not deployed\n\nIf the shared flow specified in the `\u003cSharedFlowBundle\u003e` element of the Flow Callout policy, is not deployed, then this error occurs.\n\nFor example, If the `\u003cSharedFlowBundle\u003e` element in the Flow Callout policy contains a shared flow called `Shared-Flow_example` which is not deployed in the specific environment in which the API request is made, then the error occurs.\n\nExample Error Message \n\n {\n \"fault\": {\n \"faultstring\": \"Shared Flow Shared-Flow_example Not Found\",\n \"detail\": {\n \"errorcode\": \"flow.SharedFlowNotFound\"\n }\n }\n }\n\nDiagnosis\n\n1. Identify the shared flow which is not deployed. You can find this in the `faultstring` element of the error response. For example, in the following `faultstring`, the shared flow name is `Shared-Flow_example`:\n\n `\"faultstring\": \"Shared Flow Shared-Flow_example Not Found\"`\n2. In the UI, check if this shared flow is deployed.\n\n For example, you will notice in the below screenshot that the shared flow `Shared-Flow_example` exists but is not deployed.\n\n Since this shared flow is not deployed, you receive the error code: \n\n flow.SharedFlowNotFound\n\nResolution\n\nEnsure that the shared flow specified in the `\u003cSharedFlowBundle\u003e` element in the Flow Callout policy, exists and deployed in the specific environment in which the API request is executed.\n\nTo correct the above example, deploy the shared flow called `Shared-Flow_example` in the test environment. The following screenshot shows that the shared flow `SharedFlow_Sample` is deployed:\n\nIf you make an API call to the test environment, you will no longer see the\nerror, because the Flow Callout is deployed to the test environment as well."]]
