Dear team,
We’ve encountered an issue in our keypad codes creation -
Our logic is as follows :
-
When a code is needed, we first check if it exists already by getting (GET auth all the auth of a lock
-
If no auth with the expected name is returned, we generate (PUT auth) auth for it with a random code.
Else (it exists in the GET auth response), we are making an update to the existing auth that keeps the same code.
The issue we have is as follows:
-
On October 19, We’ve been required to create or update a code for lock 440601317 with name “booking-355593”.
-
We’ve made a GET auth and as expected, there was no auth for it yet.
-
a Few seconds later, we’ve created the required auth using the PUT auth
-
We’ve received a 204 response from your servers that the auth created.
-
On October 25, We’ve been required to create or update the code for lock 440601317 with name “booking-355593”.
6. We’ve made a GET auth, but surprisingly it was not in the response.
- a Few seconds later, we’ve created the required auth using the PUT auth - This part should not have happened if (5) was returning the expected response.
Given the above info - can you please explain why the auth with the 13 and named “booking-355593” was not returned on October 25?
Attached, please find the logs screenshots from all of the steps:
-
Response of GET auth on October 19
-
Request to PUT auth on October 19
-
Response of PUT auth on October 19
-
Response of GET auth on October 25
