Meraki

CarolineD

In my case I just had a time.sleep(60) and it works well, so no big deal, I just have to wait some times that I wasn't waiting for before Looks like the "claimed" command made earlier wasn't already passed. Usually it makes less than 10sec, but today more like 60sec. (experienced on several sites, not juste one) I just wondered if there is an explanation, and if I can reduce this timing soon. Especially when I deploy and configure multiples sites in parallel.

CarolineD

Hi, Since now, when I deployed a MX thanks to the API, I was able to modify his config with API also in the 5-10 second after the claim. Modifications are like renaming, add traffic policy, etc. But since this morning, I have to wait some seconds (I didn't count exactely but put some time.sleep(60) to be sure. meraki.exceptions.APIError: appliance, updateDeviceApplianceUplinksSettings - 404 Not Found, <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtmplease wait a minute if the key or org was just newly created. Does someone have a clue about it ? Thanks

Meraki

Community

About CarolineD

CarolineD

Community Record

Badges

Re: Change with API after a claim

Change with API after a claim