Skip to content
justcrawl.io

node_type_unknown

node_type_unknown

Section titled “node_type_unknown”

HTTP status: 400 Bad Request

How to fix

Section titled “How to fix”
  1. Check the spelling of every nodes[].type value. Valid node types are: entry, split, service, storage, extractor, warehouse, result, failure_terminal.
  2. Check for legacy names. bigdata is the legacy name for warehouse; failed is the legacy name for failure_terminal. Both legacy names are still accepted with a Deprecation: true response header — but new workflows should use the new names.
  3. Confirm the type is lowercase. Node types are case-sensitive. Entry or SERVICE won't match.
  4. Confirm you're sending the workflow JSON, not a string of it. Double-encoded workflows fail at the parse step (you'll see invalid_workflow before this).

What this means

Section titled “What this means”

The workflow JSON parsed and the DAG shape is valid, but one of the nodes[].type values doesn't match any node type the worker knows how to execute. The param field on the error body names the offending node.

Section titled “Related errors”

Still stuck?

Section titled “Still stuck?”

Contact support with your request_id (looks like req_01HF3JKB...). Include the offending node so we can confirm the spelling against the canonical types.