Troubleshooting

Messages you may see, and what to do about them.

Message	Meaning and remedy
`unknown top-level key "…" (title, params, nodes)`	Only those three keys are allowed at the top. Check indentation.
`node … starts with …: a node's first step reads data`	Put `series`, `regions`, `from` or `join` first.
`node … reads "…", which is not a node`	A `from`, `join` or chart `from` names a node that does not exist.
`nodes read each other in a loop: a → b → a`	Break the cycle.
`… must be the node's last step`	`chart` and `map` come last.
`no column "…" (have […])`	The column does not exist at that step; the message lists the columns there are. Run, then use the editor’s suggestions.
`more than N series match (…): narrow it, or raise max_series`	Add words to `find`, add a `place`, or raise `max_series`.
`no series match …`	No series with those words; customers and artifacts for anyone with the link only see published series.
`join: say on which columns (on: [year])`	The tables share none of `time`, `year`, `month`, `code`: give `on`.
`two columns would be called …`	A `select` or `rename` produces a duplicate name.
`the Lab is busy running other workbooks`	Three runs are already in progress; try again in a moment.
`nothing to commit`	The YAML is the same as the head commit’s.
`this snapshot includes data that is not public`	A staff artifact taken on all data cannot go out by link; saving it as Anyone with the link takes it again on public data.
An artifact asks you to sign in	It is shared with a team or with named people; sign in with the account it was shared with.