Skip to main content

Troubleshooting Zendesk Reader

This topic outlines common symptoms, likely causes, and recommended resolutions for running the Zendesk Reader in Striim.

API rate limit exceeded (HTTP 429)

Symptoms: application halts or retries due to 429 responses.

Resolution:

  • Increase Polling interval to reduce request frequency.

  • Reduce Thread pool count and/or MaxConnections.

  • Lower Fetch size (maximum 100).

  • Limit Objects to the minimal set needed; avoid broad % usage.

Initial load interrupted cannot resume

Cause: initial load recovery is not supported.

Resolution: rerun the initial load. If you need continuity, capture the time you began the initial load and use that time as the Start Timestamp for a subsequent incremental run.

Invalid Fetch size

Symptoms: request failures or validation errors when Fetch size is set above the allowed maximum.

Resolution: set Fetch size to a value ≤ 100.

No data returned for selected object

Possible causes:

  • Secondary object selected without its required primary object (for example, comments- or metrics-related objects without tickets).

  • Object name case mismatch (object names must be all lowercase).

Resolution: include the required primary object(s) and ensure all entries in Objects and Excluded objects are lowercase.

Authentication errors

Symptoms: failed sign-in, invalid or expired token, or 401/403 responses.

Resolution:

  • For OAuth, regenerate the access token and re-enter it when Auth Flow is enabled.

  • For username/password or API token modes, verify credentials and account permissions, then retest the connection.

  • Confirm the Connection URL matches your Zendesk subdomain.