With the following flow;    1 - I have a device claimed into a network  2 - I remove this device from the network  (https://developer.cisco.com/meraki/api-v1/#!remove-network-devices)  3 - I claim this device into another organization  (https://developer.cisco.com/meraki/api-v1/#!claim-into-organization)  4 - I claim this device into another network in this new organization  (https://developer.cisco.com/meraki/api-v1/#!claim-network-devices)   Sometimes this flow works file with no problems, and sometimes I get "Device with serial '1111-1111-1111' is already claimed" error while doing step 3. For the cases I get this error, if I wait for around 10 minutes and try again from step 3, the flow succeeds.   So in some cases, the api falsely thinks the device is already claimed in a network. Any ideas why this could be happening?   What I suspect is, if the 2 organizations are on different shards, it takes some time for the data to be replicated between shards after step 2. Facts supporting this theory are,  1 - operation succeeds after some time  2 - this consistently happens for some organization pairs, and consistently not happens for some organization pairs.this be the cause? ... View more

We are using the api to clone an organization ( https://developer.cisco.com/meraki/api-v1/#!clone-organization )   This call automatically copies organization-level settings and config templates. It works fine for low number of config templates, but when the organization has more than 14-15 config templates, api call times out.   I have tried to clone an organizaton that has 25 config templates via the dashboard (and not via the api), and the operation succeeded in around 2 minutes. So indeed, looking like the time it takes for the clone to run is proportional to the number of config templates, and it can be done over the dashboard as they do not have a timeout there, but can't be done via the api because of the 60-second hard timeout.   I checked action batches as well but this operantion is not supported by action batches.   Any idea how we can make this work via the api, for organizations that have more then ~15 config templates? ... View more

For syslog server settings, on the API docs, it is stated that valid options for role field are these: 'Wireless event log', 'Appliance event log', 'Switch event log', 'Air Marshal events', 'Flows', 'URLs', 'IDS alerts', 'Security events'   I have a combined (wireless / security / switch) network. For this network, I can successfully create a syslog server if I include any subset of role options except 'IDS alerts' and 'Security events'. If I include any one of these two, I get a 400 error with the following message: 'Please select at least one valid role for server_address:port'. I also don't see these 2 roles as options on the dashboard.   Is there a specific network type, account feature or anything for which these syslog role types are enabled? If that is the case, can I get that info from the API? Or maybe are these role types deprecated? ... View more

I'm trying to get network client events through the dashboard api. Most of the time, the request returns a 502 response after waiting around 60 seconds. Other times, it returns the response in around 1 second. I've tried with different values of "perPage" parameter and the result is the same.    Anyone having a similar issue? ... View more

I have been trying to get a snapshot for a specific timestamp (and that's because when fetching without a timestamp, I'm having the same issue as here: https://community.meraki.com/t5/Developers-APIs/Snapshot-API-not-working-404/m-p/45294)   My tests show that the timestamp works when sent in San Francisco's time zone, not working with utc, and not with the network's time zone. Could not find any documentation on this. Is it true that the parameter works in SF timezone only, or am I missing something, maybe a header parameter? ... View more