It looks like there is a bug in the service right now, where any malformed correlation Id will result in an HTTP status code of 500, which the SDK will turn into a ServerErrorException with a response body and exception message of:
{ "Message": "{\"errorCode\":500001,\"trackingId\":\"b18e47205f024726923046c53de3067d-G:0-TimeStamp:08/02/2021 18:27:03\",\"message\":\"InternalServerError\",\"timestampUtc\":\"2021-08-02T18:27:03.2607187Z\"}", "ExceptionMessage": "" }
My contact on the service team will get a fix in, but I don't have an ETA yet.