-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal error encountered. - not catchable #932
Comments
Hello, May I receive some assistance here, please? Thanks |
Hello Chirag, Sorry for keeping you waiting. I didn't realize you've created this issue. Will take a look soon. Knack |
Hello Knack,
Yes correct.
================= PHP EXTENSION INFORMATION And do you still face this issue when running the same query? (I can check your query internally, so you don't need to share it here)
|
Could you please also share the version of |
I have also included the gax version information in my previous response. gax/1.19.1
|
Hi Chirag, I'm trying to reproduce the error you got, but so far I cannot do it yet. Having said that, from the error you shared on the forum, it looks like the library should be able to recognize the error because the type is Digging deeper, I think that the internal error you got probably is not an Could you help me verify this? Maybe you can add something around that if clause to check if my assumption is true. |
Hi Knack,
Yes, it is. Yesterday, I encountered an internal error. However, when I attempted to debug the issue, I was unable to reproduce the error while rerunning the same example. As a result, I'm not entirely certain about the nature of the problem. Thanks, |
OK. Please let me know when you can reproduce it. If it's not even an |
I have faced same issue again.
I think you are right its not creating instance of ApiException.
Thanks, |
Is it not even |
Yes, This is not even honoured Exception. |
That's weird. We may need to file a bug on the gax-php repo. |
Ok. |
Taking a look at your recent report again, it looks like it was thrown as |
Yes, It wasn't caught at the last catch? |
That's quite weird, since it says that the uncaught exception is |
Yes, But I was getting out of loop when Internal Error encountered and cron jobs are killed. |
[DO NOT INCLUDE ANY PERSONAL OR SENSITIVE DATA - MAKE SURE TO REDACT CONTENT WHEN NECESSARY]
Your question:
The encountered internal error is not catchable. I attempted to catch the error using various methods, but but it was not catchable. Instead, it simply breaks the cron process.
Private Reply by forum:
Reference: https://groups.google.com/g/adwords-api/c/tkvPnT-fmMo/m/IYS31igSAgAJ
How I can catch error which falls under Internal error encountered.
Thanks,
The text was updated successfully, but these errors were encountered: