API Failing In Some Cloud Instance With Invalid OData Query Options ErrorCode 1000

News Knowledge Base
1

Why is an API request working fine in some Cloud instance but in some others, following error is thrown "{\"message\":\"Invalid OData query options.\",\"errorCode\":1000,\"traceId\":\}"

Issue Description:
When calling API requests on Automation Cloud instances, the requests are failing for specific fields with the following error message 

"{\"message\":\"Invalid OData query options.\",\"errorCode\":1000,\"traceId\":\}"


Validation/ Resolution:
This is expected to be caused by having the Strict API setting enabled for the specific Tenant. Usually, this setting is enabled by default for new tenants, but existing tenants need to be opted in manually.

Below are the steps to enable it manually,

  1. Navigate to Orchestrator> Tenant > Settings > General
  2. Scroll down to "API Settings" and disable the checkbox selected
  3. Save the configurations

  1. Enabling this setting will make certain API fields become non-filterable and/or non-sortable, thus helping prevent performance issues. (Refer)

Refer Orchestrator - Managing Logical Resources to identify if the fields in the request are filterable by default.

1 Like