---
title: "Handle Silent HTTP 200 GraphQL Errors in Workday — Kiweely"
description: "Why Workday Graph API returns HTTP 200 OK even when queries or mutations fail, how to inspect the errors array in Orchestrate, and how to fix v1 vs v4 AMD…"
url: https://kiweely.com/guides/workday-graphql-http-200-silent-mutation-errors
---

# Handling Silent GraphQL Errors in PMD and Orchestrate When HTTP Status Returns 200 OK

Workday Graph API endpoints return HTTP 200 OK even when a query or mutation fails with an S21 or validation error inside the JSON errors array. Inspect $.errors explicitly in Orchestrate and verify that your .amd base URL version matches Graph API Explorer.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   3 min read
-   Published November 6
-   By Kiweely

## Why Workday Graph API failures return HTTP `200 OK`

Unlike Workday REST APIs—which return HTTP `400`, `403`, `404`, or `500` when a request fails—the Workday Graph API (`/graphql/v1` through `/graphql/v4`) follows the GraphQL specification and returns an HTTP `200 OK` status code whenever the request reaches the GraphQL execution engine, even if the query or mutation itself fails.

When a mutation fails because of an invalid Workday ID (`S21`), missing domain security (`S22`), or a business rule violation, the HTTP status code is still `200`, the target field under `"data"` is set to `null`, and the actual HTTP-equivalent status code (`400`, `403`, `404`) is nested inside `"errors[].extensions.statusCode"`:

json

```
{
  "data": {
    "myApp_abcdde_updateProjectRecord": null
  },
  "errors": [
    {
      "extensions": {
        "code": "S21",
        "path": [],
        "statusCode": 400
      },
      "locations": [
        {
          "column": 305,
          "line": 1
        }
      ],
      "message": "not found: zzzz598104b617d290081e315bb417f40000",
      "path": [
        "myApp_abcdde_updateProjectRecord"
      ]
    }
  ]
}
```

Because standard error handlers in Workday Orchestrate and `failOnStatusCodes` rules on HTTP steps only trigger on non-`2xx` transport status codes, an orchestration calling the Workday Graph API will mark the step as succeeded and continue executing downstream steps with `null` data unless you explicitly inspect the JSON body for `"errors"`.

## Catching GraphQL `errors[]` inside Workday Orchestrate

When invoking a GraphQL query or mutation inside an orchestration (via **Send Workday Graph API Request** or **Send Workday API Request**), add an explicit validation check immediately after the Graph API step before reading any fields from `$.data`.

### Pattern 1: Fail and route to the Error Handler with `Continue on Conditions`

Place a **Continue on Conditions** step directly after your Graph API step so that any non-empty `errors` array raises a step exception and triggers your local or global Error Handler:

javascript

```
// Continue only when HTTP status is 200 AND the GraphQL errors array is empty
data.SendGraphApiRequest.isSuccess.and(
  data.SendGraphApiRequest.response
    .asJSON()
    .stringAtJsonPathWithDefault("$.errors[0].message", "")
    .isEmpty()
)
```

In the **Validation Message** field of the **Continue on Conditions** step, dynamically surface the exact Workday error code and message from the GraphQL payload so it appears in **Orchestration Activity**:

javascript

```
"GraphQL mutation failed ["
  .append(
    data.SendGraphApiRequest.response
      .asJSON()
      .stringAtJsonPathWithDefault("$.errors[0].extensions.code", "UNKNOWN")
  )
  .append("]: ")
  .append(
    data.SendGraphApiRequest.response
      .asJSON()
      .stringAtJsonPathWithDefault("$.errors[0].message", "No error message returned")
  )
```

### Pattern 2: Branching on partial errors inside a Loop

If your orchestration processes records in a loop and you want to log failed GraphQL mutations without halting the entire run, place a **Branch on Conditions** step inside the loop:

-   **Branch 1 (`Has GraphQL Error`):** Condition `!data.SendGraphApiRequest.response.asJSON().stringAtJsonPathWithDefault("$.errors[0].message", "").isEmpty()` -> route to an **Integration Message** step (`Severity: Error`) logging the failed record ID and `$.errors[0].message`.
-   **Branch 2 (`Success`):** Proceed with reading `$.data.<mutationName>.workdayID.id`.

## Why a Graph mutation works in Graph API Explorer (`v4`) but does nothing from a PMD page (`v1`)

A second silent failure occurs on Presentation Metadata (`PMD`) pages when a mutation—such as `updateWorkerTimeBlock` or a custom object mutation—updates the tenant record when tested in **Graph API Explorer**, but returns `200 OK` from your PMD `outboundEndPoints` without updating the object in the tenant:

json

```
{
  "outboundEndPoints": [
    {
      "name": "updateTimeBlock",
      "baseUrlType": "workday-graph",
      "authType": "sso",
      "graphQuery": {
        "query": "mutation updateWorkerTimeBlock($updateWorkerTimeBlock_input: TimeTracking_TimeBlockView_UpdateInput!, $updateWorkerTimeBlock_timeBlockId: IdentifierInput!, $updateWorkerTimeBlock_workerId: IdentifierInput!) { updateWorkerTimeBlock(input: $updateWorkerTimeBlock_input, timeBlockId: $updateWorkerTimeBlock_timeBlockId, workerId: $updateWorkerTimeBlock_workerId) { status { descriptor workdayID { id } } } }",
        "variables": {
          "updateWorkerTimeBlock_input": {
            "status": {
              "id": {
                "type": "Time_Tracking_Set_Up_Option_ID",
                "id": "SUBMITTED"
              }
            }
          },
          "updateWorkerTimeBlock_timeBlockId": {
            "id": "9632e55bb572900a606d9d8e0b6d0001",
            "type": "WID"
          },
          "updateWorkerTimeBlock_workerId": {
            "id": "19f7dabb79994d29931cd139df6272ed",
            "type": "WID"
          }
        }
      }
    }
  ]
}
```

### Fix: Align the `.amd` Graph API base URL version with Graph API Explorer

**Graph API Explorer** defaults to the latest Graph API schema version (such as `v4`), whereas many starter `.amd` (Application Metadata) files define `workday-graph` or `workday-graphql` pointing to `/graphql/v1`:

json

```
{
  "baseUrls": [
    {
      "key": "workday-graph",
      "url": "https://api.workday.com/graphql/v4"
    }
  ]
}
```

When a mutation or input field was introduced or updated in `v4` (for example, `updateWorkerTimeBlock`), sending that mutation to `/graphql/v1` can fail or ignore fields that do not match the `v1` schema. Open your `.amd` file, check the `"baseUrls"` entry for `"workday-graph"` / `"workday-graphql"`, and update the path to the exact schema version (`/graphql/v4`) you selected in **Graph API Explorer**.

## How to verify the fix in your tenant

1.  In **Orchestration Builder**, run a test execution passing a deliberately invalid Workday ID (`zzzz598104b617d290081e315bb417f40000`) into your GraphQL mutation step.
2.  Verify that the **Continue on Conditions** step catches `$.errors[0].message`, stops execution, and prints the `[S21]: not found` message in **Orchestration Activity** instead of reporting the orchestration as `Completed`.
3.  For PMD Graph mutations, verify that the `/graphql/v<N>` version in `.amd` matches the version dropdown in **Graph API Explorer**, submit the page, and confirm the target record updates in the tenant.

## Sources checked

-   [Graph API in Orchestrations](https://developer.workday.com/documentation/uyb1682465360107)
-   [Graph API Mutations](https://developer.workday.com/documentation/kbu1671067116723)
-   [Graph API Explorer](https://developer.workday.com/documentation/jfi1654276754280)
-   [Submit Graph API Mutations on a Page](https://developer.workday.com/documentation/pnn1671585287177)
-   [Reference: Workday Graph API](https://developer.workday.com/documentation/flw1653707569144)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying Workday Graph API queries fail with DataSourceFilter is inaccessible when the caller lacks View access to the domain securing the filter, and silently return blank fields on processingWorker when Employee As Self lacks contact domain permissions.](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)
-   [### Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API Workday Graph API mutations require nested IdentifierInput objects for single-instance relationships like createdBy—which you can generate cleanly in PMD with graph:createId(id). To clear an existing single-instance relationship back to null, use the Model Business Object REST PUT or PATCH API.](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)
-   [### Why Attachment Model Components and contentType Are Missing from the GraphQL Schema After Migrating to IMPL After promoting a Workday Extend app with an Attachment Business Object to an Implementation or Sandbox tenant, GraphQL queries can fail with Unknown type \_DataSources or missing contentType fields. Refresh the model cache, verify ISU domain security, and check tenant Graph schema availability.](https://kiweely.com/guides/workday-graphql-attachment-schema-contenttype-missing-impl)
-   [### Why WQL Queries on findCandidates and allWorkers Return Empty Right After a Business Process Step WQL queries triggered during a Workday business process often return zero rows for two distinct reasons: the transaction has not committed yet, or the query reads an eventually consistent indexed data source like findCandidates. Trigger on Completed status or pass launch parameters directly.](https://kiweely.com/guides/wql-indexing-delay-findcandidates-bp-status-change)

### More guides on Orchestrate

[All 86 guides](https://kiweely.com/guides#orchestrate)

-   [Avoiding the 25-Second Synchronous Timeout When an Extend Page Calls External LLM APIs Through Orchestrate](https://kiweely.com/guides/workday-extend-async-orchestration-llm-timeout)
-   [Why Log to File Turns XML Closing Tags into <// and How to Write #if Conditions in CreateTextTemplate](https://kiweely.com/guides/workday-orchestrate-xml-double-slash-log-to-file-if-conditions)
-   [Waiting for Import\_Payroll\_Input\_Request Background Processes at Scale in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-wait-background-process-import-payroll-input)
-   [Why Workday sub-orchestrations and BP orchestrations show Completed when an API call fails](https://kiweely.com/guides/workday-orchestrate-sub-orchestration-completed-on-api-error)
-   [Why stripHtmlTags and htmlToPlainText Leave HTML Tags Over 2,003 Characters in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-striphtmltags-2003-character-limit)
-   [Sorting JsonKeyValueIterator Collections and Numeric String Values in Workday Orchestrate Loops](https://kiweely.com/guides/workday-orchestrate-sort-jsonkeyvalueiterator-numeric-sorting)
-   [Why SendWorkdayRaasRequest returns 401 Unauthorized or empty data via the cloud proxy](https://kiweely.com/guides/workday-orchestrate-sendworkdayraasrequest-401-cloud-proxy)
-   [Reusing and versioning sub-orchestrations across Workday Extend and O4I apps](https://kiweely.com/guides/workday-orchestrate-reuse-sub-orchestrations-across-apps)

### From the blog on Orchestrate

[All posts](https://kiweely.com/blog)

-   [Keep in Studio, Move to Orchestrate, or Rebuild as an Extend App? A Practical Triage Matrix](https://kiweely.com/blog/migrating-legacy-workday-studio-integrations-to-orchestrate-decision-matrix)
-   [How Kiweely Vine designs, builds, deploys, tests and monitors a Workday Orchestration for Integration](https://kiweely.com/blog/workday-orchestration-for-integration-with-kiweely)
-   [Why Workday Studio Remains Essential in an Orchestrate World](https://kiweely.com/blog/why-workday-studio-still-matters-with-orchestrate)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
