Troubleshooting: Workday Live Data Query

HTTP ERROR 404 Not Found

The client successfully connected to the server, but the specific address/endpoint it asked for doesn't exist on that server.

The port is incorrect.

Modify the connection port to 443.

HTTP 400 Bad Request

The Workday Authorization Server received your request but refused to process it because the information sent was invalid.

The request payload is syntactically invalid or contains incorrect parameters.

Confirm the ISU name matches the

View Integration System User

task.

HTTP 401 Unauthorized

The Workday Authorization Server received the request but refused to validate the identity of the application due to invalid or unrecognized credentials.

A failure occurred in the authentication process due to invalid or unrecognized credentials.

Ensure that the Client ID specified in your configuration aligns with the one generated during the

task.

Access token request failed due to network error

Application was unable to establish a stable connection to the remote server to request an OAuth2 access token.

This signifies that the application was unable to establish a TCP/IP connection with the specified authorization endpoint, preventing the authentication handshake from initiating.

Ensure that the Token Endpoint URL is syntactically correct and aligns with the specific Workday environment you are attempting to access (example: PROD, SBOX, IMPL).

Failed to obtain access token - 404

Indicates successful connection to the server, but the specific OAuth2 Token Endpoint requested does not exist at that location.

An error occurred during the token exchange.

Ensure the Token Endpoint URL is correct.

Failed to obtain access token - 401

Error during the token exchange signifies a Cryptographic Authentication Failure.

Mismatch between the local private key used for signing and the public key registered in the Workday API Client.

Ensure that the local private key utilized is correct.

Objects or fields are missing from the LDQ connection

Either:

The objects aren’t available in Data Cloud. See the Data Cloud Catalog for a list of objects that are available.

The ISU or user-as-self account you’re using to authenticate the LDQ connection doesn’t have access to the objects.

If the object is available in Data Cloud, add the domain for the object to one of the security groups that the ISU or user-as-self account has access to. See Edit Domain Security Policies.

If you make security group changes after the client connection has been established, subsequent permission changes might take up to 15 minutes to propagate before users can access newly authorized tables or columns.