Starting today, API messages to note hub to set a config.db are being dropped despite the Request responding with 200 OK. Last message that got through was 20hrs ago. Any idea what is going on? Notehub status says that everything is operational. What steps need to be taken to fix this?
Would you give us some more detail? Which API are you using? What is the AppUID?
Request is:
Posting Config to Notehub: https://api.notefile.net/v1/projects/app:d2373e7d-8f60-4502-9c81-14ea1d73c1c3/devices/sn:ltered-S3-1/notes/config.db/scenario
Recently discovered that there is in an err field in the json response despite returning 200 OK.
HTTP Response: {'err': '{no-acct} not registered: <client-id>'} Status Code: 200
I deleted the api key which was 2 years old and generated a new one but it still exhibits the same issue. Appreciate the help.
@szygmunt This started happening to me today as well. @tjvantoll did something on the API change?
@jcsalem Apologies Jim, I see you are with Blues but tagged TJ. The same issue started today a few hours ago with the no-acct error
Thanks for reporting this. It seems this is a bug in our last release and I think we’ve tracked it down. We are working on a fix
We believe we’ve fixed this issue. Would you retest?
Note that even though it was reporting the no-acct error, the API call was still succeeding.
1 Like
Re-tested and it is working now. Thank you! I don’t think the api call was succeeding though as there was no record on note hub and no response from the end units. Appreciate the help.
Thank you for clarifying whether the API succeeded previously. We should not have returned a 200 if that was the case. I’ll make sure that doesn’t happen if an error is detected.