## TL;DR
Configure the datasource in the recipe before scanning: PipeRider cannot profile a datasource the recipe does not define, so add the connection to the PipeRider configuration or the recipe, using the same connection name the recipe expects. PipeRider separates the recipe, which says what to profile, from the datasource configuration, which says where the data lives. A recipe moved without its configuration fails exactly like this.

```text
PipeRider scan failed error "profiling recipe datasource not configured"
```

## Use this when
- The check or run fails with this symptom: a PipeRider scan fails with profiling recipe datasource not configured.
- You are working on a PipeRider project profiling a database or a warehouse table from a recipe and the failure repeats on the same data or configuration.
- You need the failing rows, rule, or stage isolated before changing thresholds or code.

## Not for this skill when
- A datasource that was removed on purpose, where the recipe should be retired rather than reconnected.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Open the recipe and note the datasource name it references. Verify: the expected connection name is known
2. Check the PipeRider configuration in the project and in the user level config. Verify: the named datasource is absent from both
3. Add the datasource with its connection details and the exact referenced name. Verify: the configuration resolves the recipe reference
4. Run a connection check for the datasource. Verify: the connection succeeds
5. Run the scan. Verify: profiling completes and produces a report

## Variant phrasings
### piperider profiling recipe datasource not configured
The shorter phrasing focused on the named failure.
### piperider scan failed datasource not configured
The symptom phrasing a searcher tries next.
### piperider recipe datasource setup fix
The variant naming the failing stage or tool directly.

Compatibility: PipeRider recipes and datasource configuration

## Why it happens
Recipes are portable files teams share and version, while datasource configuration often lives in a local or user level file that does not travel with the recipe. Running a shared recipe on a new machine or in CI reproduces this failure until the datasource is defined there.

## Edge cases / pitfalls
- Connection details for shared recipes belong in environment backed configuration, not committed into the recipe file.
- Name drift between environments, such as dev versus the recipe default, causes the same error; standardise the default name.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AcjEwLgbPdlGgqPO-cR_JQ