-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
exception __get_data() session get response is not OK204 #82
Comments
I redacted some personal info in your issue. You do not want that to be found on the internet. The error is not very specific, but when ik can find the time I will take a look at it. |
Ohh, thank you, I did not notice. |
This issue is stale because it has been open for 30 days with no activity. |
Hey, I'm getting the same error - maybe slightly different area of code? I added 3 extra debug lines to try and figure it out on my own. I'll do some more digging later and maybe get new tokens and go from there.. What's odd is the refresh token is a guid? maybe that's ok, in the past refresh tokens have been token looking
|
Hi, did you solve the problem? |
Dear Yo-ha!
Thank you for your work!
I have a little issue.
The new integration (2024.3.1) working fine, but no data is received.
I tried to write the optional PatientID, too.
The oldiest integration (2024.1.0) brought the informations.
The debug log:
What could be the problem?
Thank you for your help!
The text was updated successfully, but these errors were encountered: