[[["わかりやすい","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 documentation covers troubleshooting steps for common deployment errors in Apigee and Apigee hybrid related to cache configurations.\u003c/p\u003e\n"],["\u003cp\u003eAn "InvalidTimeout" error occurs when the \u003ccode\u003e<CacheLookupTimeoutInSeconds>\u003c/code\u003e element in a LookupCache policy is set to a negative value, and the solution is to ensure this value is a non-negative integer.\u003c/p\u003e\n"],["\u003cp\u003eAn "InvalidCacheResourceReference" error occurs when the \u003ccode\u003e<CacheResource>\u003c/code\u003e element references a cache name that doesn't exist in the target environment, requiring verification and creation of the cache in the correct environment.\u003c/p\u003e\n"],["\u003cp\u003eThe "CacheNotFound" error indicates that a specific cache mentioned in the error message has not been created on a specific Message Processor component, requiring you to contact Apigee Support for assistance.\u003c/p\u003e\n"]]],[],null,["*You're viewing **Apigee** and **Apigee hybrid** documentation.\nView [Apigee Edge](https://docs.apigee.com/api-platform/troubleshoot/policies/deployment/lookup-cache-deployment-errors) documentation.*\n| Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().\n\nInvalidTimeout\n\nError Message\n\nDeployment of the API proxy through either the Apigee UI or API fails with this error message: \n\n```\nError Saving Revision revision_number\nCacheLookupTimeoutInSeconds value value should be greater than zero.\n```\n\nExample Error Message \n\n Error Saving Revision 2\n CacheLookupTimeoutInSeconds -1 value should be greater than zero.\n\nExample Error Screenshot\n\nCause\n\nIf the `\u003cCacheLookupTimeoutInSeconds\u003e` element of a [LookupCache policy](/apigee/docs/api-platform/reference/policies/lookup-cache-policy) is set to a negative number, then the deployment of the API proxy fails.\n\nFor example, if the `\u003cCacheLookupTimeoutInSeconds\u003e` element is `-1`, then the deployment of the API proxy fails.\n\nDiagnosis\n\n1. Identify the invalid value specified for the `\u003cCacheLookupTimeoutInSeconds\u003e` element in the [LookupCache policy](/apigee/docs/api-platform/reference/policies/lookup-cache-policy). You can find this information in the error message. For example, in the following error, the invalid value used for `\u003cCacheLookupTimeoutInSeconds\u003e` element is `-1`:\n\n CacheLookupTimeoutInSeconds -1 value should be greater than zero.\n\n2. Examine all the LookupCache policies in the specific API Proxy where the failure has occurred. There could be one or more LookupCache policies in which the `\u003cCacheLookupTimeoutInSeconds\u003e` element is specified. Identify the LookUpCache policy where the invalid value (identified in step #1 above) is specified for `\u003cCacheLookupTimeoutInSeconds\u003e` element.\n\n For example, the following policy configuration specifies the value of `\u003cCacheLookupTimeoutInSeconds\u003e` of `-1`, which matches the error message: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cLookupCache async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"LookupCache-Token\"\u003e\n \u003cDisplayName\u003eLookupCache-Token\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cCacheKey\u003e\n \u003cPrefix/\u003e\n \u003cKeyFragment ref=\"request.queryparam.client_id\"/\u003e\n \u003c/CacheKey\u003e\n \u003cCacheLookupTimeoutInSeconds\u003e-1\u003c/CacheLookupTimeoutInSeconds\u003e\n \u003cScope\u003eExclusive\u003c/Scope\u003e\n \u003cExpirySettings\u003e\n \u003cTimeoutInSec\u003e3600\u003c/TimeoutInSec\u003e\n \u003c/ExpirySettings\u003e\n \u003cAssignTo\u003eusertoken\u003c/AssignTo\u003e\n \u003c/LookupCache\u003e\n\n3. If the `\u003cCacheLookupTimeoutInSeconds\u003e` is specified as a negative integer, then that's the cause of the error.\n\nResolution\n\nEnsure that the value for the `\u003cCacheLookupTimeoutInSeconds\u003e` element of the LookupCache policy is always specified as a non-negative integer.\n\nTo correct the example LookupCache policy shown above, you could modify the `\u003cCacheLookupTimeoutInSeconds\u003e` element to `30`. \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cLookupCache async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"LookupCache-Token\"\u003e\n \u003cDisplayName\u003eLookupCache-Token\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cCacheKey\u003e\n \u003cPrefix/\u003e\n \u003cKeyFragment ref=\"request.queryparam.client_id\"/\u003e\n \u003c/CacheKey\u003e\n \u003cCacheResource\u003etokencache\u003c/CacheResource\u003e\n \u003cCacheLookupTimeoutInSeconds\u003e30\u003c/CacheLookupTimeoutInSeconds\u003e\n \u003cScope\u003eExclusive\u003c/Scope\u003e\n \u003cExpirySettings\u003e\n \u003cTimeoutInSec\u003e3600\u003c/TimeoutInSec\u003e\n \u003c/ExpirySettings\u003e\n \u003cAssignTo\u003eusertoken\u003c/AssignTo\u003e\n \u003c/LookupCache\u003e\n\nInvalidCacheResourceReference\n\nError 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 [populate_cache_policy_name]. Context Revision:[revision_number];APIProxy:ResponseCache;Organization:[organization];Environment:[environment]\n```\n\nExample Error Message \n\n Error Deploying Revision 2 to test\n Invalid cache resource reference tokencache in Step definition LookupCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\nExample Error Screenshot\n\nCause\n\nThis error occurs if the `\u003cCacheResource\u003e` element is set to a name which does not exist in the environment where the API proxy is being deployed.\n\nDiagnosis\n\n1. Identify the invalid cache used in `\u003cCacheResource\u003e` element of the [LookupCache policy](/apigee/docs/api-platform/reference/policies/lookup-cache-policy) and the environment where the error occurred. You can find both of these items in the error message. For example, in the following error, the name of the invalid cache is `tokencache` and the environment name is `test`.\n\n Invalid cache resource reference tokencache in Step definition LookupCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\n2. Examine all the LookupCache policies in the specific API Proxy where the failure has occurred. Identify the specific LookupCache policy where the invalid cache (identified in step #1) is specified in `\u003cCacheResource\u003e` element is specified.\n\n For example, the following policy specifies the value of `\u003cCacheResource\u003e` as `tokencache`, which matches the error message: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?\u003e\n \u003cLookupCache async=\"false\" continueOnError=\"false\" enabled=\"true\" name=\"LookupCache-Token\"\u003e\n \u003cDisplayName\u003eLookupCache-Token\u003c/DisplayName\u003e\n \u003cProperties/\u003e\n \u003cCacheKey\u003e\n \u003cPrefix/\u003e\n \u003cKeyFragment ref=\"request.queryparam.client_id\"/\u003e\n \u003c/CacheKey\u003e\n \u003cCacheResource\u003etokencache\u003c/CacheResource\u003e\n \u003cCacheLookupTimeoutInSeconds/\u003e\n \u003cScope\u003eExclusive\u003c/Scope\u003e\n \u003cExpirySettings\u003e\n \u003cTimeoutInSec\u003e3600\u003c/TimeoutInSec\u003e\n \u003c/ExpirySettings\u003e\n \u003cAssignTo\u003eusertoken\u003c/AssignTo\u003e\n \u003c/LookupCache\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 \u003cbr /\u003e\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 LookupCache-Token. Context Revision:2;APIProxy:TestCache;Organization:kkalckstein-eval;Environment:test\n\nResolution\n\nEnsure that the cache name specified in the `\u003cCacheResource\u003e` element has been created in the environment where you want to deploy the API proxy.\n\nCacheNotFound\n\nError 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\nExample Error Message \n\n```\nError Cache : configCache, not found in organization : kkalckstein-eval__test\n```\n\nCause\n\nThis error occurs if the specific cache mentioned in the error message has not been created on a specific Message Processor component.\n\nResolution\n\nContact [Apigee Support](https://apigee.com/about/support/portal) for assistance."]]
![[Environment Configuration Caches] タブ。](https://cloud.google.com/static/apigee/docs/api-platform/images/lookupcache-error-3.png?authuser=0000&hl=ja)