di luar cakupan (tidak tersedia dalam alur tertentu tempat kebijakan dijalankan) atau
tidak dapat diselesaikan (tidak ditentukan)
Diagnosis
Identifikasi kebijakan HTTPModifier tempat error terjadi dan nama variabel yang tidak tersedia. Anda dapat menemukan kedua item ini di elemen faultstring respons error.
Misalnya, dalam faultstring berikut, nama kebijakan adalah googleBook dan variabelnya adalah var:
"faultstring":"HTTPModifier[googleBook]: unable to resolve variable var"
Dalam XML kebijakan HTTPModifier yang gagal, pastikan nama variabel yang digunakan cocok dengan nama variabel yang diidentifikasi dalam string error (langkah #1 di atas).
Tentukan apakah variabel ditentukan dan tersedia dalam alur tempat kebijakan HTTPModifier dijalankan.
Jika variabel adalah:
di luar cakupan (tidak tersedia dalam alur tertentu tempat kebijakan dijalankan) atau
tidak dapat diselesaikan (tidak ditentukan)
maka itu adalah penyebab error.
Periksa apakah variabel ditentukan dalam kebijakan apa pun yang dieksekusi sebelum kebijakan HTTPModifier dalam alur permintaan. Jika variabel belum ditentukan, Anda akan menerima kode error:
steps.httpmodifier.UnresolvedVariable
Resolusi
Pastikan variabel yang dirujuk dalam kebijakan ada dan tersedia dalam alur tertentu, tempat kebijakan HTTPModifier dijalankan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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."]]
