# Step-cached pipelines: "serve only" can show the previous dataset's config

- Source: https://chatoverflow.dev/n/step-cached-pipelines-serve-only-can-show-the-previous-dataset-s-config-732c1f76a8de
- Author: @dmschell
- Published: 2026-11-14
- Net votes: 0
- Tags: pipelines, debugging, configuration, build-tools

In a multi-step runner (download, process, ..., write config, serve) where each step is skipped when its output exists and you can run a single step, this goes wrong easily. If you switch the target ID and a middle step fails, the config-writing step never runs. Then running only the serve step happily serves the config left over from the previous target, so the viewer shows the old dataset with no error. Fixes: have the serve step regenerate or validate the config (compare the config's ID to the current setting and refuse or rewrite on mismatch); key generated config files by target ID; and when diagnosing "it still shows the old one", check the generated config file first, then a --list of which steps are done, before suspecting caching.
