-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Resource not found when calling Zenpy.chats.triggers() #625
Comments
Sorry it's taken me so long to get look at this. Thank you for your investigation. I'll triage this further and see if I can remediate it with/for you. |
I've found the source of the bug. It's around here: Line 485 in c1fc2b8
I'm going to try to figure out what the most "correct" course of action is. |
@LucasCiocari Do you think you could try to consume #626 and test? |
Worked perfectly! |
OK I'll schedule some time to merge and then bump. |
When upgrading to zenpy 2.0.35 from 2.0.25 it was noticed that the Zenpy.chats.triggers() method was now returning an exception:
APIException: {"error": "ResourceNotFound", "description": "The requested resource could not be located or does not exist"}
During exploration of the library to find the issue, it was noticed that the call
Zenpy( ... ).chats.triggers._get(insp._build_url(endpoint=insp.endpoint()))
returned the results just fine.When setting log level to debug, it seems that the call being made on
Zenpy().chats.triggers()
is hitting the endpointhttps://www.zopim.com/api/v2/triggers/True
instead ofhttps://www.zopim.com/api/v2/triggers
Zenpy().chats.triggers()
debug result:while
Zenpy( ... ).chats.triggers._get(insp._build_url(endpoint=insp.endpoint()))
returns
I believe this change might have something to do with it:
https://github.com/facetoe/zenpy/compare/2.0.25...2.0.35?diff=unified&w=#diff-85faba355a00935e5032c0aae05af1c9c73049fb720c1f7dba33c0454da6160cR202
These tests were done with version 2.0.45 but confirmed that in version 2.0.47 the error still occurs.
The text was updated successfully, but these errors were encountered: