Skip to main content

Troubleshooting ServiceNow Reader

The following known limitations and common issues can affect ServiceNow Reader behavior.

  • DELETE operations not captured: The reader emits INSERT and UPDATE operations only. Deleted rows in the source will not be removed at the target. Consider soft-delete flags or target-side reconciliation if needed.

  • Incremental prerequisites: Incremental capture relies on timestamp columns such as sys_updated_on (and sys_created_on for some tables). Tables without suitable timestamps may require full sync behavior each polling cycle.

  • Batch API payload limits: When using Batch API, requests are subject to ServiceNow size limits (for example, ~10 MB per batch). If batches exceed limits, reduce Fetch size, increase Polling interval, or disable Batch API.

  • Rate limiting and throttling: HTTP 429 or slow responses indicate ServiceNow rate limits. Increase Polling interval, tune Fetch size, or lower concurrency (Thread pool count / Max connections).

  • Insufficient privileges (ACLs): Missing roles or ACL permissions can cause read failures or empty results. Validate required roles (for example, admin, snc_read_only) or configure per-table ACLs appropriately.

  • Timestamp format mismatches: Start timestamp must use UTC in YYYY-MMM-DD HH:MM:SS format. Invalid formats will be rejected.

  • Connectivity and timeouts: Increase Connection timeout and Connection retries if network latency or transient errors occur. Verify TLS and firewall rules.