We have an issue and we do not know if it's by design. When we log apim.getError() in an API's catch and we can check "policyTitle" indicating the policy causing an error as following:

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": "Check framework validation code"}

But when we migrated the catch to the error global policy, now it's null.

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": null}

How can I get the same behavior in the error global policy catch?

Update: I found a workaround for this problem long ago, but I wanted to confirm if this behavior is from IBM's APIC by design. Is "policyTitle" always set to null in the error global policy (Maybe to avoid confusing identical policy titles from different sources; pre-request global policy, assembly flow, or post-response global policy?!)?

I am assuming this because any error caught in a catch from a policy in either pre-request global policy, assembly flow, or post-response global policy contains a non-null value in "policyTitle" but not when caught in the error global policy.

Can you @Steve Linn or any of the APIC team confirm?

We have an issue and we do not know if it's by design. When we log apim.getError() in an API's catch and we can check "policyTitle" indicating the policy causing an error as following:

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": "Check framework validation code"}

But when we migrated the catch to the error global policy, now it's null.

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": null}

How can I get the same behavior in the error global policy catch?

Hi Mohamed,
I'll need to check with the developer knowledgeable with that area of the code.  I can't think of any reason why the policy title string would be lost but the rest of the error object is unchanged, so this may be a product issue.  I'll hopefully get some more information soon, but I'd suggest you open a PMR to get a more official answer.
Best Regards,
Steve Linn

Update: I found a workaround for this problem long ago, but I wanted to confirm if this behavior is from IBM's APIC by design. Is "policyTitle" always set to null in the error global policy (Maybe to avoid confusing identical policy titles from different sources; pre-request global policy, assembly flow, or post-response global policy?!)?

I am assuming this because any error caught in a catch from a policy in either pre-request global policy, assembly flow, or post-response global policy contains a non-null value in "policyTitle" but not when caught in the error global policy.

Can you @Steve Linn or any of the APIC team confirm?

We have an issue and we do not know if it's by design. When we log apim.getError() in an API's catch and we can check "policyTitle" indicating the policy causing an error as following:

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": "Check framework validation code"}

But when we migrated the catch to the error global policy, now it's null.

"Message": {     "name": "JavaScriptError",     "message": "Internal Error",     "status": {         "code": 500,         "reason": "Internal Server Error"      },      "policyTitle": null}

How can I get the same behavior in the error global policy catch?