[[["容易理解","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-09-04 (世界標準時間)。"],[[["\u003cp\u003eThe "InvalidCacheResourceReference" error occurs when an InvalidateCache policy references a cache name that does not exist in the target environment during API proxy deployment.\u003c/p\u003e\n"],["\u003cp\u003eTo diagnose "InvalidCacheResourceReference," check the error message for the InvalidateCache policy name, invalid cache name, and environment, then verify the cache definition within that environment.\u003c/p\u003e\n"],["\u003cp\u003eThe "CacheNotFound" error means that a cache required by the API proxy has not been created on a Message Processor component.\u003c/p\u003e\n"],["\u003cp\u003eThe resolution for "InvalidCacheResourceReference" is to ensure the cache specified in the InvalidateCache policy's \u003ccode\u003e<CacheResource>\u003c/code\u003e element is created in the deployment environment.\u003c/p\u003e\n"],["\u003cp\u003e"CacheNotFound" error resolution is handled by contacting Apigee Support.\u003c/p\u003e\n"]]],[],null,["# Invalidate Cache policy deployment error troubleshooting\n\n*You're viewing **Apigee** and **Apigee hybrid** documentation.\nView [Apigee Edge](https://docs.apigee.com/api-platform/troubleshoot/policies/deployment/invalidate-cache-deployment-errors) documentation.*\n| Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().\n\nInvalidCacheResourceReference\n-----------------------------\n\n### Error Message\n\nDeployment of the API proxy through either the Apigee UI or API fails with this error message: \n\n```\nError Deploying Revision revision_number to environment\nInvalid cache resource reference [cache_resource] in Step definition [invalidate_cache_policy_name]. Context Revision:[revision_number];APIProxy:[apiproxy_name];Organization:[organization];Environment:[environment]\n```\n\n### Example Error Message\n\n Error Deploying Revision 2 to test\n Invalid cache resource reference tokencache in Step definition InvalidateCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\n### Example Error Screenshot\n\n### Cause\n\nThis error occurs if the `\u003cCacheResource\u003e` element in the InvalidateCache policy is set to a name that does not exist in the environment where the API proxy is being deployed.\n\n### Diagnosis\n\n1. Identify the [InvalidateCache policy](/apigee/docs/api-platform/reference/policies/invalidate-cache-policy) name, the invalid cache used in `\u003cCacheResource\u003e` element of the InvalidateCache policy, and the environment where the error occurred. You can find all these items in the error message. For example, in the following error, the InvalidateCache policy name is `InvalidateCache-Token`, the name of the invalid cache is `tokencache`, and the environment name is `test`.\n\n Invalid cache resource reference tokencache in Step definition InvalidateCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\n2. Examine the failed InvalidateCache policy XML and verify if the cache name specified for the `\u003cCacheResource\u003e` element matches with the error message.\n\n In this example, the cache name specified in the `\u003cCacheResource\u003e` element is `tokencache`: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cInvalidateCache async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"InvalidateCache-Token\"\u003e\n \u003cDisplayName\u003eInvalidateCache-Token\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cCacheKey\u003e\n \u003cPrefix/\u003e\n \u003cKeyFragment ref=\"\"/\u003e\n \u003c/CacheKey\u003e\n \u003cCacheResource\u003etokencache\u003c/CacheResource\u003e\n \u003cScope\u003eExclusive\u003c/Scope\u003e\n \u003cCacheContext\u003e\n \u003cAPIProxyName/\u003e\n \u003cProxyName\u003edefault\u003c/ProxyName\u003e\n \u003cTargetName\u003edefault\u003c/TargetName\u003e\n \u003c/CacheContext\u003e\n \u003cPurgeChildEntries\u003efalse\u003c/PurgeChildEntries\u003e\n \u003c/InvalidateCache\u003e\n\n3. Verify if the cache (determined in step #1) has been defined in the specific environment (identified in step #1).\n\n In the Apigee UI, navigate to **ADMIN \\\u003e Environment \\\u003e test** and check if the cache exists in the **Caches** tab of **Environment Configuration**. If the cache does not exist, then that's the cause of the error.\n\n For example, notice in the screenshot below that the cache named `tokencache` does not exist.\n\n Because the cache named `tokencache` is not defined in the `test` environment, you get the error: \n\n Invalid cache resource reference tokencache in Step definition InvalidateCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\n### Resolution\n\nEnsure that the cache specified in the `\u003cCacheResource\u003e` element of InvalidateCache policy has been created in the environment where you want to deploy the API proxy.\n\nCacheNotFound\n-------------\n\n### Error Message\n\nDeployment of the API proxy through either the Apigee UI or API results in an error message like this, and the deployment status of the API Proxy is marked as partially deployed: \n\n```\nError: Cache : cache_resource, not found in organization : organization__environment.\n```\n\n### Example Error Message\n\n Error Cache : configCache, not found in organization : kkalckstein-eval__test\n\n### Cause\n\nThis error occurs if the specific cache mentioned in the error message has not been created on a specific Message Processor component. A Message Processor is an internal component that processes the flow of API traffic through Apigee.\n\n### Resolution\n\nContact [Apigee Support](https://apigee.com/about/support/portal) for assistance."]]
