Inconsistent error formats returned from cube cloud

[Josh-a-e]

Describe the bug
Sometimes errors have an "error" property, sometimes they have a "message" property.

Expected behavior

A consistent attribute to denote the details of an error.

Screenshots

Version:
0.30.66

Context

I'm polling cube cloud to determine if my deployments have taken effect.

[paveltiunov]

@Josh-a-e Hey Joshua! Could you please share which API you're calling and with what parameters?

[Josh-a-e]

Hey - sure, I'm just hitting the regular query endpoint using cubeClient.load({ ... }) to poll cube cloud to discover whether or not my deployment has been completed yet.

const token = jwt.sign({ STATUS_CHECK: 'OK' }, jwtSecretKey, {
  expiresIn: '2s',
});
const cubeClient = cubejs(token, {
  apiUrl: url,
});

// ...

const serviceQuery = await cubeClient.load({
  dimensions: ['Service.key', 'Service.value'],
  order: { 'Service.key': 'asc' },
});

I have this wrapped in a catch / retry loop, in which there is

const jwtTokenError =
  // If we update the JWT secret key the signed JWT will initially be invalid until it takes effect
  hasStatusAndResponse(error) &&
  error.status === 403 &&
  error.response?.error === 'Invalid token'; // <- "error" and not "message" like the other two below

const serviceTimeoutError =
  hasStatusAndResponse(error) &&
  error.status === 504 &&
  error.response?.message === 'Gateway Timeout';

const serviceUnavailableError =
  hasStatusAndResponse(error) &&
  error.status === 503 &&
  error.response?.message === 'Service Unavailable';

[Josh-a-e]

Looks like this is fixed?

[paveltiunov]

@Josh-a-e Yep. This one was fixed.