Genesys Cloud CLI analytics query 422 - invalid interval

General Discussion
1
  • genesyscloud analytics conversations details query returns 422 Unprocessable Entity
  • Error: “Interval start must be before interval end”
  • ISO 8601 timestamps: start=“2023-10-01T00:00:00+11:00”, end=“2023-10-01T01:00:00+11:00”
  • CLI version 1.0.48
  • Terraform provider 1.12.0
  • Manual API call via Postman works with same payload
  • Suspect CLI timestamp parsing ignores timezone offset
  • Anyone facing this with Sydney timezone?
2

genesyscloud analytics conversations details query
–start “2023-09-30T11:00:00Z”
–end “2023-09-30T12:00:00Z”


Switching to UTC (`Z`) usually resolves the parsing ambiguity in the CLI. Coming from Zendesk, where timestamps are often handled loosely in the UI, this strict ISO 8601 enforcement in Genesys Cloud initially feels rigid. However, the CLI parser seems to struggle with specific regional offsets like `+11:00` when calculating the interval delta, even if the API accepts it directly.

Using UTC ensures the start and end times are unambiguous for the client-side validation logic. It mirrors how we had to standardize ticket creation timestamps during our migration to avoid reporting gaps. If the data looks correct in Postman but fails in the CLI, the issue is almost certainly local timestamp interpretation. Standardizing on UTC also helps when comparing these analytics reports against Zendesk’s historical data exports, which typically default to UTC regardless of user timezone settings.
3

Try forcing UTC in the CLI command to bypass the offset parsing glitch.

genesyscloud analytics conversations details query --start "2023-09-30T11:00:00Z" --end "2023-09-30T12:00:00Z"

The +11:00 offset often trips up the internal delta calculator. Switching to Zulu time keeps the interval logic clean and avoids that 422 error entirely.