> ## Documentation Index > Fetch the complete documentation index at: https://docs.platform.toloka.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Pipeline errors and how to fix them > Find an error message by screen, identify its cause, and follow the fix. The platform shows these errors while you build, deploy, or run a pipeline. Each appears here exactly as shown, with its cause and fix. Search this page for the exact text on your screen, and note that ``, ``, and similar placeholders stand for the parts of a message that change. ## In the Issues window You meet these when you deploy. The **Issues** window collects them: errors block the deploy, and warnings can be overridden. See [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) for how the gate sorts them. Search the families below for your exact message. If it is not here, it restates a setting's documented bounds. The Other pre-deploy messages section points to the page that owns it. ### Graph wiring | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Missing connection for output handle "" in node ""` | A node output, or a Match branch, connects to nothing. | Connect every output on the path from Start to End, or remove the node. | — | | `Infinite cycle: → → …` | The graph loops, so an item could never leave it. | Remove or re-route one edge in the listed loop. | — | | `Handle "" of node "" references unknown field ""` | The node still points at a field that was deleted. | Re-bind the node's fields, or ask the agent to fix the reference. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Required field "" is not available at input handle "" of node ""` | No upstream node provides this required field on that path. | Produce the field upstream, mark the input optional, or re-route the edge. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Required field "" is only optionally provided at input handle "" of node ""` | The field is required here, but the upstream node may leave it empty. | Make the upstream output required, or mark this input optional. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Optional field "" is not available at input handle "" of node ""` | An optional input names a field no upstream node provides. | Remove the optional input, or produce the field upstream. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | ### Labeling interface sample data | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Code is required` | The labeling interface has not been built yet. | Ask the agent to build it. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | | `Data is not valid JSON` | The interface's sample data does not parse. | Fix the sample-data JSON. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Data must be a JSON object` | The sample data parses but is not an object. | Make the sample data an object keyed by input name. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Data is missing required input ""` | The sample data has no value for a required input. | Add a sample value for the input. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Data for input "" does not match its schema` | The sample value has the wrong type or shape. | Fix the sample value to match the field's type. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Data has unexpected key "" that does not match any input` | The sample data names a field the node does not read. | Remove the stray key. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | ` has minDurationSec () greater than maxDurationSec (). minDurationSec must be less than or equal to maxDurationSec` | A video control in the interface sets a minimum duration longer than its maximum, on a data-collection node. | Lower the minimum or raise the maximum so the minimum is not longer, or ask the agent to fix the control. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | ### Field type schema | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Invalid JSON schema: not valid JSON` | The field's type schema does not parse as JSON. | Fix the schema JSON, or ask the agent to regenerate the field type. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Invalid JSON schema: must be a JSON object` | The type schema is JSON but not an object. | Replace it with a JSON-object schema. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Invalid JSON schema:
` | The type schema does not compile. `
` names the problem. | Fix the reported schema problem. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | ### Node names and settings | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `The name must be between 4 and 32 characters long` | The node's name is shorter than 4 or longer than 32 characters. | Rename the node to between 4 and 32 characters. | — | | `The name must start with a letter, can contain only lowercase letters, numbers and underscores, and must end with a letter or number` | The node's name uses characters the format forbids, or does not start and end as required. | Rename it to `lowercase_with_underscores` form: start with a letter, use only lowercase letters, numbers, and underscores, and end with a letter or number. | — | | `The name must be unique across all nodes` | Another node already uses this name. | Rename one of the two nodes so every node name is different. | — | | `The description exceeds the maximum of 150000 characters` | The node's description is longer than 150000 characters. | Shorten the description to 150000 characters or fewer. | — | | `This setting exceeds the maximum of 150000 characters` | The total text in one of the node's settings exceeds 150000 characters. | Shorten that setting's content to 150000 characters or fewer. | — | ### Field structure | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Entity type must be one of the supported core entity types: ` | A field's type is missing or is not one the platform supports. `` names the supported types. | Give the field one of the listed types, or ask the agent to fix it. | — | | `Relations must reference existing entities` | A field relation points at a field that no longer exists. | Re-link the relation to an existing field, or remove it. | — | | `Output entities must have at least one relation to another entity` | On a node with more than one field, an output field has no relation to another field. | Relate the output to the field it builds on. | — | ### Onboarding examples These are warnings, so you can override them and deploy anyway. | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Example check paths do not match any output entity jsonPath of the node: ` | An onboarding worked-example's checks target locations that none of the node's output fields use. `` lists them. | Point the checks at the node's output locations, or override the warning. | — | | `Examples gated only by llm checks, with no golden-backed deterministic check: ` | An onboarding worked-example is scored only by an LLM check, with no exact or code check to grade it deterministically. `` lists the examples. | Add a golden-backed check (an exact or code check) to the example, or override the warning. | — | ### Other pre-deploy messages Most other messages in the **Issues** window restate a setting's documented bounds, such as a name length, a step count, or a price floor. The message names the setting. For node settings, see [Code node](https://docs.platform.toloka.ai/docs/data/reference/nodes/code.md), [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md), [Quorum node](https://docs.platform.toloka.ai/docs/data/reference/nodes/quorum.md), [Match node](https://docs.platform.toloka.ai/docs/data/reference/nodes/match.md), and [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md). For quality settings, see [Quality control](https://docs.platform.toloka.ai/docs/data/concepts/quality-control.md); for offboarding rules, see [Quorum node](https://docs.platform.toloka.ai/docs/data/reference/nodes/quorum.md#offboarding-rules). See [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) for check cases and their run states, [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) for field descriptions, and [Label with an LLM instead of experts](https://docs.platform.toloka.ai/docs/data/guides/synthetic-labeling.md) for synthetic-only settings. ### Lint checks Lints start automatically after saved edits. Required lints must finish before deployment. See [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) for the available kinds and finding severities. | Message | Cause | How to fix | | - | - | - | | `Check "" has not started yet; lints start automatically a few seconds after the graph is applied` | The lint is waiting to start on the saved configuration. | Wait for it to finish. If it does not start, click **Run lints** in **Issues**. | | `Check "" has not run on the current graph and dataset; run the pipeline's lints` | No current lint result is available. | Click **Run lints**, or ask the agent to run the lints. | | `Check "" is still running` | The check has not finished. | Wait for its result before deploying. | | `Check "" failed: ; run the pipeline's lints again` / `Check "" failed; run the pipeline's lints again` | The lint failed or timed out. | Read the error, correct the cause if needed, and click **Run lints**. | ## On a check card A check card shows these in its **Error** section after a run fails. See [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) for what each check kind does and when to run it. | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `No quality criteria configured on this node` | Annotation Quality Assurance ran with no criteria on the node. | Add quality criteria, then rerun the check. | [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) | | `LLMQA check requires LLM QA to be enabled on this node (evaluation_result proxies are missing)` | The node has no LLM review: **Human Only** review on Generation, or **No QA, Offboarding Only** on Quorum. | Set **Quality Assurance** to **LLM Only** or **Hybrid** on Generation, or **LLM Only** on Quorum, then rerun Annotation Quality Assurance. | [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) | | `Invalid check input: ` | A Code Test case's input JSON stopped parsing. | Fix the case's JSON input. | [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) | | `Invalid check input JSON` | An Annotation Quality Assurance case has invalid JSON in Task Input or Task Output. | Fix the case's JSON input. | [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) | | `Execution output must be an object` | A Code Test run returned something other than a dictionary. | Make the code return a dictionary. | [Code node](https://docs.platform.toloka.ai/docs/data/reference/nodes/code.md) | | `Missing required field: ""` / `Unknown field: ""` / `Field "" exceeds the maximum size of 32KB (actual: KB)` / `Field "": ` | The check's input or returned output breaks the node's field contract or the 32 KB per-value cap. | Fix the case input, or fix the node's code and fields so the output matches its declared contract. | [Code node](https://docs.platform.toloka.ai/docs/data/reference/nodes/code.md) | ## On the Items tab The run's **Items** tab records these as an item's failure reason, on the item and in its trace. | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `This item is missing a value for the required input "".` | The item entered the run with no value for a required Start input. | Fill the value in the dataset, or mark the input optional. A later run labels the item only if its own dataset, filter, and limit still select it — a failed status is not a retry trigger. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `This item is missing values for required inputs: "", "".` | Several required Start inputs have no value for the item. | Fill the missing values in the dataset, or mark those inputs optional. A later run labels the item only if its own dataset, filter, and limit still select it — a failed status is not a retry trigger. | [Fields and data](https://docs.platform.toloka.ai/docs/data/concepts/fields-and-data.md) | | `Insufficient funds to reserve the node cost` | The team balance ran out mid-run, and the run paused. | Top up the balance, then press **Resume**. | [Billing](https://docs.platform.toloka.ai/docs/core/billing.md#pipeline-runs) | | `Missing required field "" ()` / `Unknown field proxy ()` / `Field "" () exceeds the maximum size of 1024KB (actual: KB)` / `Field "" (): ` | The Code node's returned output breaks its declared field contract or the 1 MB per-value cap. | Fix the code to return every required declared field, only declared fields, matching types, under 1 MB each. | [Code node](https://docs.platform.toloka.ai/docs/data/reference/nodes/code.md) | | `Dynamic entity "" () has instances, exceeding the max of ` | A repeating input arrived with more values than the field's maximum. | Raise the field's maximum (up to 50), or reduce the upstream values. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | | `Required field proxy '' is missing` | A Match test read a required field with no recorded value. | Mark the tested input optional, or guarantee the value upstream. | [Match node](https://docs.platform.toloka.ai/docs/data/reference/nodes/match.md) | | `Invalid JSONPath '': ` | A Match test's location does not evaluate. | Fix the test's location expression. | [Match node](https://docs.platform.toloka.ai/docs/data/reference/nodes/match.md) | | `JSONPath '' resolved to values, expected a single value` | A Match test's location matches more than one value. | Narrow the location so it resolves to at most one value. | [Match node](https://docs.platform.toloka.ai/docs/data/reference/nodes/match.md) | ## When you deploy or launch You meet these when you confirm a deploy, or when you set what a run will launch on the Start node. | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Insufficient balance to deploy this pipeline. Add funds to your team and restart the deploy.` | The team balance is below the deploy minimum at deploy time. | Add funds, then deploy again. A failed deploy frees the pipeline. | [Billing](https://docs.platform.toloka.ai/docs/core/billing.md#pipeline-runs) | | `Your team’s balance () is too low to deploy this pipeline. Add funds to your team to continue.` | The balance is below the deploy minimum when you confirm. | Add funds, then reopen the deploy. | [Billing](https://docs.platform.toloka.ai/docs/core/billing.md#pipeline-runs) | | `Cannot create run for pipeline because it already has an active run.` | The pipeline already has a run whose deploy did not fail (a run that failed at run time still counts). | Clone the pipeline and deploy the clone. | [How data labeling works](https://docs.platform.toloka.ai/docs/data/concepts/overview.md) | | `Cannot deploy pipeline ( validation error): ` | The server revalidated at deploy and found blocking errors. | Fix the listed issues. Each also appears in the Issues window. | [Self-check](https://docs.platform.toloka.ai/docs/data/concepts/self-check.md) | | `This run would launch items, more than the maximum of 10000. Set "Max items to launch" to 10000 or fewer, or narrow the filter.` | The selected item count exceeds the per-run limit. | Set **Max items to launch** to 10,000 or fewer, or narrow the filter. | [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md#max-items-to-launch) | | `This pipeline run would process items, which exceeds the maximum of 10000 items per pipeline run` | The selection exceeds the limit when the run is created. | Reduce the item limit or narrow the filter, then retry. | [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md#max-items-to-launch) | | `In "" you tried to reuse audience from a pipeline that wasn't deployed. Please select a different node from this project or choose "Do not reuse audience".` | Audience reuse points at a node with no recorded deployment. | Point reuse at a deployed node, or turn reuse off. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | | `In "" you tried to reuse audience from a pipeline you don't have access to. Please select a node from this project or choose "Do not reuse audience".` | Audience reuse points at another team's pipeline. | Point reuse at one of your team's nodes, or turn reuse off. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | | `Cannot disable onboarding when reusing WFR from a node that was deployed with onboarding (/)` | A reusing node turned onboarding off while its source deployment had it on. | Turn onboarding back on, or stop reusing that audience. | [Generation node](https://docs.platform.toloka.ai/docs/data/reference/nodes/generation.md) | | `Only item match the current filter. Lower the limit or widen the filter.` | The item limit is higher than the number of matching items. | Lower the limit, or widen the filter. | [Label a large dataset in batches](https://docs.platform.toloka.ai/docs/data/guides/label-at-volume.md) | | `This run would launch items, more than the maximum of 10,000 per run. Set “Max items to launch” to 10,000 or fewer, or narrow the filter.` | The launch count is over the per-run limit of 10,000 items. | Set **Max items to launch** to 10,000 or fewer, or narrow the filter. | [Label a large dataset in batches](https://docs.platform.toloka.ai/docs/data/guides/label-at-volume.md) | | `Pipeline input field not present in this dataset: ` | Bound inputs name fields the current dataset lacks. | Refresh fields and re-bind, or switch to a dataset that has them. | [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md) | | `The item filter references dataset fields that no longer exist. Clear the filter to recompute item counts correctly.` | The filter references removed dataset fields. | Clear the filter, then rebuild it. | [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md) | | `Dataset already has field(s) "", … with an incompatible JSON schema. Rename the field proxies, edit the dataset fields' schemas, or remove the conflicting dataset fields, then retry.` | A pipeline field (usually an output) has the same name as an existing dataset field but an incompatible type, so the deploy fails instead of overwriting it. | Rename the conflicting pipeline field so the deploy creates a new dataset field, or point the pipeline at a new dataset, then deploy again. Dataset field types cannot be changed, despite what the message suggests. | [Label a large dataset in batches](https://docs.platform.toloka.ai/docs/data/guides/label-at-volume.md) | | ``The provided `itemFilter` references field IDs that do not exist on the selected dataset.`` | The agent relays this when a requested filter names fields the new dataset lacks after a dataset switch. | Ask the agent to rebuild the filter against the new dataset's fields. | [Start and End nodes](https://docs.platform.toloka.ai/docs/data/reference/nodes/start-and-end.md) | ## On the dataset page You meet these on a dataset's own page, when you upload a file, derive fields, append items, or filter the table. See [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) for the tasks behind them. | Message | Cause | How to fix | Where the rule lives | | - | - | - | - | | `Please upload a JSON, JSONL or CSV file.` | The dropped or chosen file is none of JSON, JSONL or CSV. | Upload a `.json`, `.jsonl` or `.csv` file. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `File is empty` | The file is 0 bytes. | Upload a file that has content. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `File is too large (max 1024 MB).` | The file is over the 1024 MB per-file limit. | Split the data into files of 1024 MB or under. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Please select only 1 file.` | More than one file was dropped at once. | Drop one file at a time. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `File size exceeds maximum allowed size of 1024MB` | The uploaded file is over the 1024 MB limit. The server rejected it. | Upload a file of 1024 MB or under. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Another upload is already in progress. Complete or cancel it before starting a new one.` | The dataset already has an upload running. It takes one at a time. | Wait for it to finish, or cancel it, then upload again. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Cannot ingest into existing field "uploaded": its schema differs from the upload field schema` | The dataset already has a field named `uploaded` with a custom type, so the upload cannot store into it. | Uploads cannot use that field. Create a new dataset and upload there. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `File is malformed (could not parse ).` | The file does not parse as the format it was read as — JSON, JSONL or CSV, or a JSON root that is not an array. For JSONL the message names the offending line. | Repair the file in the format it was read as: a JSON array of objects, one JSON object per line, or a CSV with a header row and one row per item. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `File must contain at least one item.` | The file's array is empty. | Add at least one item to the file. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Validation failed with error(s):`, followed by one line per bad item: `Item at index exceeds the maximum allowed size of 1.00 MiB (actual: )` / `Item at index does not match field "" JSON Schema` | One or more items failed validation, so nothing was written. The list stops at 50. | Fix the listed items (shrink any over 1 MB), then upload again. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Dataset item cap reached; remaining rows were not imported.` | The upload hit the 150,000-item cap. The items up to the cap were kept. | Upload fewer items, or split the data across datasets. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Schema incompatible with existing upload ( issue(s)):`, followed by one line per issue: `Field "" () is present in existing upload but missing in new upload` / `: type "" is not present in existing schema` / `: existing schema has enum constraint but new schema does not` / `: enum value "" is not present in existing schema` / `: existing schema has array items constraint but new schema does not` / `.: property exists in existing schema but is missing in new schema` | An appended file's shape does not match the first upload's fields. | Make the appended file's fields match the first upload's names and types, then append again. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Dataset has reached the maximum of 500 fields` | The dataset already has 500 fields. | Use a new dataset, or derive fewer fields. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Adding field(s) would exceed the maximum of 500 fields (currently )` | The batch of new fields would push the dataset over 500. | Create fewer fields, or use a new dataset. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Field "" has reached the maximum of 500 revisions per item` | A field on one item already holds 500 recorded values. | Point new derivations at a different target field, or use a new dataset. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Value-based filter is not supported on field(s) : revisions exceed the 32KB preview limit. Use the "no revision" filter or filter by source instead.` | The field's largest value is over 32 KB, so it cannot be filtered by value. | Filter that field by source, or by missing value, instead. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Invalid JSONPath: ` | The filter's location expression does not parse. | Fix the location. Use `$` for the whole value. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Choose a value filter, source filter, or “No revision for this field”.` | Apply was clicked with no filter set. | Set a value, a source, or the no-value option, then apply. | [Create and manage datasets](https://docs.platform.toloka.ai/docs/core/datasets.md) | | `Derived field validation failed:`, followed by one line per bad entry: `- "": name already exists in dataset` / `- "": duplicate name in batch` / `- "