Skip to main content
Version: 1.1.0

Troubleshooting

Report run fails immediately

Possible causes:

  • Server URL is not the REST services root.
  • Network or firewall restrictions block access.
  • Authentication is required but session is missing.

What to do:

  1. Confirm URL format ends at /rest/services.
  2. Open the URL in a browser and verify it responds.
  3. Re-authenticate from the Servers view.

Services return Critical unexpectedly

Possible causes:

  • Endpoint outage or timeout.
  • Empty layers/tables after data pipeline failure.
  • Spatial reference or extent mismatch.

What to do:

  1. Open the service in Services detail and run Audit.
  2. Check failed assertions for exact reason.
  3. Compare with REST JSON output to isolate data vs configuration issues.

Saved server shows expired session

What to do:

  1. Use Check to verify current auth state.
  2. Click Re-auth if token is expired.
  3. Re-run report after successful sign-in.

Schedule not running as expected

Possible causes:

  • Schedule is disabled.
  • Interval is longer than expected.
  • App closed without background mode enabled.

What to do:

  1. Confirm schedule toggle is enabled.
  2. Verify interval value.
  3. Enable Run in background if needed.

Dependency analysis cannot find references

Possible causes:

  • Wrong service URL or item ID.
  • Insufficient Portal access permissions.
  • References exist in external orgs not in your search scope.

What to do:

  1. Re-check URL or item ID input.
  2. Verify login has access to relevant content.
  3. Provide portal URL override when auto-detection fails.