Repository navigation
Release v4.225.1
The specification run endpoint now accepts the graph specifications the runner reports, so a model that declares them gets its results instead of a 502.
Fixed
POST /stage/semantic/specifications/runheld the runner's report to the slice specifications and rejected the graph specifications it also carries, answering502 The specification runner produced an invalid or mismatched reportfor every model with a graph specification. A report is now held to the model's graph specifications too: each record must be one the model declares and appear once, and an unscoped run must report them all.