hi. I managed to work around this by using the startingAfter parameter (although documentation says that client should not use this). It seems that if I don't do it, Meraki will try to do a full extract. Some of the clients with highest traffic causes it to crash ... View more

... egg on my face - thanks for the heads up, I'll make sure we've rolled forwards to the latest version! ... View more

Cheers guys 🙂 ... View more

That's odd, our solution is still using an older version of the NodeJS SDK (1.1.0) and has recently started receiving the same error:   { errorMessage: 'HTTP Response Not OK', errorCode: 400, errorResponse: `{"errors":["'copyFromNetworkId' must be a string"]}` }   It appears to me that the API has recently changed it's behaviour in how it treats the presence (or in our case, absence) of this field. This violates the promise of backwards-compatible changes documented here.   Our previously working automation is broken ahead of our HQ rollout - can you please advise whether the API will be fixed to it's original behaviour? ... View more