Closed Carmezim closed 3 years ago
Hi @Carmezim. This is an API-side limitation, documented in the relevant endpoint. Programmatically, one would add a delay to handle this.
Since this is not an issue with the SDK, I will close this case.
Thanks for the reply.
Is it documented?
https://developer.cisco.com/meraki/api-v1/#!update-device
Could you please point me in the right documentation where this is at?
Thank you
On Mon, Mar 15, 2021 at 6:47 PM John M. Kuchta @.***> wrote:
Closed #151 https://github.com/meraki/dashboard-api-python/issues/151.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/meraki/dashboard-api-python/issues/151#event-4461415558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6A2CU7HOQT3UZNEOPFD3LTD2E75ANCNFSM4ZHAW2XQ .
Hi @Carmezim,
In https://api.meraki.com/api/v1/openapiSpec, under the claim endpoint docstrings:
"/networks/{networkId}/devices/claim": { "post": { "description": "Claim devices into a network. (Note: for recently claimed devices, it may take a few minutes for API requsts against that device to succeed)", "operationId": "claimNetworkDevices",
Current Behavior: Whenever a device is claimed, and a subsequent PUT request is made to
/devices
endpoint to update a device, the endpoint returns 404 for all attempts up to several minutes after the device has been claimed, until is then able to actually update the device returning a 200.Expected Behavior: Able to update a device info after the device has been claimed into a network without several minutes delay.
This was attempted with the SDK, using the API directly and direct HTTP with curl/Insomnia/Postman etc.
Steps to reproduce:
Any insights on that behavior or if anyone else experienced it would be great. Not sure if the best place to post this issue as it seems to be the actual Dashboard API, so if should be elsewhere please advise.
Thank you