fuori ambito (non disponibile nel flusso specifico in cui viene eseguito il criterio) o
non può essere risolto (non è definito)
Diagnosi
Identifica il criterio HTTPModifier in cui si è verificato l'errore e il nome della variabile non disponibile. Puoi trovare entrambi questi elementi nell'elemento faultstring della risposta all'errore.
Ad esempio, nel seguente faultstring, il nome del criterio è googleBook e la variabile è var:
"faultstring":"HTTPModifier[googleBook]: unable to resolve variable var"
Nel file XML della policy HTTPModifier non riuscita, verifica che il nome della variabile utilizzata corrisponda a quello identificato nella stringa di errore (passaggio 1 sopra).
Determina se la variabile è definita e disponibile nel flusso in cui viene eseguito il criterio HTTPModifier.
Se la variabile è:
fuori ambito (non disponibile nel flusso specifico in cui viene eseguito il criterio) o
non può essere risolto (non è definito)
allora è la causa dell'errore.
Controlla se la variabile è definita in uno dei criteri eseguiti prima del criterio HTTPModifier nel flusso di richiesta. Se la variabile non è stata definita, riceverai il codice di errore:
steps.httpmodifier.UnresolvedVariable
Risoluzione
Assicurati che la variabile a cui viene fatto riferimento nel criterio esista ed è disponibile nel flusso specifico in cui viene eseguito il criterio HTTPModifier.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eThis documentation addresses the \u003ccode\u003esteps.httpmodifier.UnresolvedVariable\u003c/code\u003e error in Apigee X, which occurs when a variable referenced in an HTTPModifier policy is either out of scope or undefined.\u003c/p\u003e\n"],["\u003cp\u003eThe error's \u003ccode\u003efaultstring\u003c/code\u003e provides the policy name and the specific variable that could not be resolved, which can then be used to locate the source of the problem.\u003c/p\u003e\n"],["\u003cp\u003eDiagnosis involves confirming the variable name in the HTTPModifier policy XML, then checking whether the variable is defined and available in the current flow.\u003c/p\u003e\n"],["\u003cp\u003eThe root cause is either the variable is not defined, or it exists but is not available in the flow where the HTTPModifier policy is executed.\u003c/p\u003e\n"],["\u003cp\u003eResolution involves ensuring that the referenced variable exists and is accessible within the specific flow where the HTTPModifier policy is being executed, typically by defining it in a preceding policy.\u003c/p\u003e\n"]]],[],null,["# HTTPModifier runtime error troubleshooting\n\n*You're viewing **Apigee X** documentation.\nView [Apigee Edge](https://docs.apigee.com) documentation.*\n| **Note:** Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().\n\nUnresolvedVariable\n------------------\n\n### Error code\n\n steps.httpmodifier.UnresolvedVariable\n\n### Error response body\n\n```transact-sql\n{\n \"fault\": {\n \"faultstring\": \"HTTPModifier[\u003cvar translate=\"no\"\u003epolicy_name\u003c/var\u003e]: unable to resolve variable [\u003cvar translate=\"no\"\u003evariable_name\u003c/var\u003e]\",\n \"detail\": {\n \"errorcode\": \"steps.httpmodifier.UnresolvedVariable\"\n }\n }\n}\n```\n\n### Cause\n\nThis error occurs if a variable specified in the [HTTPModifier policy](/apigee/docs/api-platform/reference/policies/http-modifier-policy) is either:\n\n- out of scope (not available in the specific flow where the policy is being executed) or\n- can't be resolved (is not defined)\n\n### Diagnosis\n\n1. Identify the HTTPModifier policy where the error occurred and the name of the variable that is not available. You can find both of these items in the `faultstring` element of the error response.\n\n For example, in the following `faultstring`, the policy name is `googleBook` and the variable is `var`: \n\n \"faultstring\": \"HTTPModifier[googleBook]: unable to resolve variable var\"\n\n2. In the failed HTTPModifier policy XML, verify that the name of the variable used matches the variable name identified in the fault string (step #1 above).\n\n3. Determine if the variable is defined and available in the flow in which the HTTPModifier policy is being executed.\n\n4. If the variable is either:\n\n 1. out of scope (not available in the specific flow where the policy is being executed) or\n 2. can't be resolved (is not defined)\n\n then that's the cause for the error.\n\n Check if the variable is defined in any of the policies that are executed before the HTTPModifier policy in the request flow. If the variable has not been defined, then you will receive the error code: \n\n steps.httpmodifier.UnresolvedVariable\n\n### Resolution\n\nEnsure that the variable referenced in the policy exists and is available in the specific flow, where the HTTPModifier policy is being executed."]]
