Wiz rejects the query with Severity cannot represent value - enum quoting rules

TL;DR

For "Severity cannot represent value: HIGH": use variables for all enum inputs and match the enum set to the query surface. Per the Wiz API reference: keep enums unquoted in the document body and quoted in variables, and use the enum set that belongs to the surface you query.

Severity cannot represent value: HIGH

Steps

1. For "Severity cannot represent value: HIGH": use variables for all enum inputs and match the enum set to the query surface.
2. Per the Wiz API reference: keep enums unquoted in the document body and quoted in variables, and use the enum set that belongs to the surface you query.

When to use

You are seeing this: In a GraphQL document literal, enums are unquoted identifiers (severity: [HIGH, CRITICAL]); in variables they are JSON strings ("severity": ["HIGH", "CRITICAL"]). Use this skill when you run into "Wiz rejects the query with Severity cannot represent value - enum quoting rules".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Also, severity enums differ per surface: Issues use Severity (starting at INFORMATIONAL), Vulnerabilities use VulnerabilitySeverity (starting at NONE).

Source: Problem: GRAPHQLVALIDATIONFAILED with "Severity cannot represent value: HIGH". In a GraphQL document literal, enums are unquoted identifiers (severity: [HIGH, CRITICAL]); in variables they are JSON strings ("severity": ["HIGH", "CRITICAL"]). Inlining quoted enums into the document body is rejected. Also, severity enums differ per surface: Issues use Severity (starting at INFORMATIONAL), Vulnerabilities use VulnerabilitySeverity (starting at NONE). Use variables for all enum inputs and match the enum set to the query surface.

Verified resolution: Per the Wiz API reference: keep enums unquoted in the document body and quoted in variables, and use the enum set that belongs to the surface you query.

Source URL: https://github.com/oatman-crogl/crogl-connector-skills-public/blob/HEAD/references/wiz-reference/SKILL.md