GraphQL 500 Error When Creating Schema Assertions

Users encountered a 500 Internal Server Error when attempting to create schema assertions through the GraphQL API. The error occurred due to a parameter that was marked as optional in the API but was actually required by the backend implementation, causing the request to fail unexpectedly.

Common Error Messages:

• HTTP 500 Internal Server Error when executing GraphQL mutation for schema assertion creation

This issue has been resolved by making the previously pseudo-optional parameter truly optional in the backend. Users can now create schema assertions without providing all parameters that were incorrectly marked as required.

To create a schema assertion using the GraphQL API:

mutation createSchemaAssertion {
  upsertDatasetFieldAssertions(
    input: {
      urn: "urn:li:dataset:(...)",
      assertions: [
        {
          # Include only required fields
          # Previously optional fields are now genuinely optional
        }
      ]
    }
  )
}

Fixed in version v0.3.13. Users on earlier versions should upgrade to v0.3.13 or later to benefit from this fix.

• Assertions Overview
• GraphQL API Reference