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