CandleStack
← All problem types

Manifest check failed

The manifest did not pass its checks, so it was not kept and the model stays as it was.

Details

  • Status422 Unprocessable Content
  • Typehttps://candlestack.tech/problems/manifest-check-failed

When it happens

  • schema - the manifest does not have the right form, for example a missing field, a value of the wrong type or a list longer than allowed.
  • catalog - a block, or its version, does not exist, or it does not fit where it is used: a block in the wrong step, session-last-candle@1 without the regular session, blesk-norm@1 on a feature it has no rule for, a feature that is not a column of the rows of the representation, or a window option last that does not fit the representation. unknown_blocks names the blocks that do not exist.
  • params - a parameter of a block has the wrong type or is out of its range.
  • names - two features have the same name, or a feature is named ts or row_id.
  • signature - signature.input is not [window length, number of features], or signature.output is not [1].
  • example - the shapes of the example do not match the signature.
  • model - the signature does not match the input or the output of the uploaded model file.

What to do

  1. 1Read problems, which says in one sentence each what is wrong, and fix those parts of the manifest.
  2. 2Take block names, versions and parameter ranges from the catalog at GET /api/v1/preprocessing/catalog.
  3. 3Send the whole manifest again; it is checked from the start.

In the response

  • problemsWhat is wrong, at most 10 items, each with check (one of the values above) and detail (one sentence).
  • more_problemsHow many more problems there are beyond the ones listed.
  • unknown_blocksBlocks the manifest names that the catalog does not have.