Esse erro ocorrerá se o elemento <CacheResource> na política InvalidateCache estiver definido como um nome que não exista no ambiente em que o proxy de API está sendo implantado.
Diagnóstico
Identifique o nome da política política InvalidateCache, o cache inválido usado no elemento <CacheResource> da política InvalidateCache e o ambiente em que o erro ocorreu. Você pode encontrar todos esses itens na mensagem de erro. Por exemplo, no erro a seguir, o nome da política InvalidateCache é InvalidateCache-Token, o nome do cache inválido é tokencache e o nome do ambiente é test.
Examine o XML com a política InvalidateCache com falha e verifique se o nome do cache especificado do elemento <CacheResource> corresponde à mensagem de erro.
Neste exemplo, o nome do cache especificado no elemento <CacheResource> é tokencache:
Verifique se o cache (determinado na etapa 1) foi definido no ambiente específico (identificado na etapa 1).
Na IU da Apigee, navegue até ADMIN > Ambiente > teste e verifique se o cache existe na guia Caches em Configuração do Ambiente. Se o cache não existir, essa é a causa do erro.
Por exemplo, observe na captura de tela abaixo que o cache tokencache não existe.
Como o cache chamado tokencache não está definido no ambiente test, você recebe o erro:
Verifique se o cache especificado no elemento <CacheResource> da política InvalidateCache foi criado no ambiente em que você quer implantar o proxy de API.
CacheNotFound
Mensagem de erro
A implantação do proxy da API por meio da IU da Apigee ou da API resulta em uma mensagem de erro como esta, e o status da implantação do Proxy da API é marcado como parcialmente implantado:
Error: Cache : cache_resource, not found in organization : organization__environment.
Exemplo de mensagem de erro
Error Cache : configCache, not found in organization : kkalckstein-eval__test
Causa
Esse erro ocorre quando o cache específico mencionado na mensagem de erro não tiver sido criado em um componente de processador de mensagens específico. Um processador de mensagens é um componente interno da Apigee que processa o fluxo de tráfego de API usando a Apigee.
Resolução
Entre em contato com o suporte da Apigee (em inglês) para receber ajuda.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-07 UTC."],[[["\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."]]
