The /api/v2/analytics/conversations/summary endpoint doesn’t accept the date range on our Berlin production tenant running Architect v24.1, returning a 400 Bad Request with invalid_time_range. Apologies for this elementary admin_ui query, but we tracked a similar drift issue during the 2022 Q3 rollout and I already aligned the ISO 8601 filters with the configuration steps you shared in that older thread. The response cuts off right after the validation check.
{"error": "invalid_time_range", "message": "start must precede end", "trace": "..."}