The Zoho Desk search API returns an HTTP 500 error when a modifiedTimeRange includes the exact timestamp 2026-03-08T02:00:00.000Z; the failure is reproducible only at that boundary while adjacent ranges succeed. [1]
What it means
The GET /api/v1/tickets/search call is hitting an internal server error inside Zoho Desk when the modifiedTimeRange parameter spans or includes 2026-03-08T02:00:00.000Z. The community report shows the same call succeeds for ranges immediately before and after that exact timestamp, and fails with {"errorCode":"INTERNALSERVERERROR","message":"An internal server error occurred while performing this operation."} when the boundary includes the timestamp. [1]
Common causes
- A server-side date/time parsing or boundary bug in the search routine that triggers only for that exact UTC timestamp. [1]
- An indexed-record edge case where a record or index entry has a corrupted or unusual value exactly at that timestamp. [1]
- A rule in the search pipeline (sorting, filtering, or aggregation) that breaks on that boundary value. The report shows removing sortBy or from did not avoid the error. [1]
- A platform-level clock/timezone transition or leap-second handling behavior that produces an unhandled state at that instant. [1]
How to fix it
- Short-term workaround: avoid calling modifiedTimeRange that includes 2026-03-08T02:00:00.000Z. Query ranges that end at 2026-03-08T01:59:59.999Z or start at 2026-03-08T02:00:00.001Z to bypass the boundary. [1]
- Retry strategy: if you must cover the boundary, split the request into two queries (before and after the exact timestamp) and merge results client-side. Use limit and pagination to keep each query small. [1]
- Reproduce and capture diagnostics: run the three test cases below and collect full request and response pairs (URL, query string, headers with Authorization masked, response body, and timestamps):
- Success case before boundary: modifiedTimeRange=2026-03-08T01:58:00.000Z,2026-03-08T01:59:59.000Z (expected 204). [1]
- Failure case hitting boundary: modifiedTimeRange=2026-03-08T01:59:59.000Z,2026-03-08T02:00:00.000Z (returns 500). [1]
- Success case after boundary: modifiedTimeRange=2026-03-08T02:00:00.000Z,2026-03-08T02:00:01.000Z (expected 204). [1]
- Open a Zoho Desk support ticket with: your Org ID, the three reproduction requests above, full response bodies, timestamps, and the exact API call (GET /api/v1/tickets/search). Ask support to check server logs for that UTC timestamp and for any index or parsing errors. The community post already documents the reproducible failure, which speeds investigation. [1]
- Monitor for a platform patch: once support confirms the root cause, schedule a switch back from the workaround to normal queries after they confirm the fix.
When to escalate
If the boundary blocks production workflows or you cannot work around it by