## TL;DR
Fix the template reference before recreating the monitor: the Sifflet monitor template points at a table field that no longer exists under that name, so open the template, find the field reference, and update it to the current field or restore the field alias. Templates reference fields by name. A renamed or dropped field breaks every monitor built from the template at once, and the error names the template because that is where the stale reference lives.

```text
Sifflet observe failed error "monitor template references missing table field"
```

## Use this when
- The check or run fails with this symptom: a Sifflet observe fails with monitor template references missing table field.
- You are working on a Sifflet deployment using monitor templates over warehouse tables 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 field that was dropped deliberately with its monitors retired, where deleting the monitors is the right outcome.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Open the failing template and note the exact field name it references. Verify: the missing field is named
2. Describe the table and compare its current fields with the template. Verify: the field was renamed, retyped, or dropped
3. Update the template reference to the current field, or add an alias in the model if other consumers use the old name. Verify: the template resolves all its fields
4. Rebuild one monitor from the template and run it. Verify: the monitor executes and reports a result
5. Rebuild the remaining monitors from the template. Verify: all template monitors run cleanly

## Variant phrasings
### sifflet monitor template references missing table field
The shorter phrasing focused on the named failure.
### sifflet observe failed missing field template
The symptom phrasing a searcher tries next.
### sifflet template field rename fix
The variant naming the failing stage or tool directly.

Compatibility: Sifflet monitor templates and warehouse table schemas

## Why it happens
Field renames in a warehouse model do not propagate into monitoring templates, which store field names as configuration. The template keeps asking for the old field, and Sifflet fails the monitor build rather than guessing which new field was meant.

## Edge cases / pitfalls
- Renaming a field back to satisfy a template can break newer consumers; update the template unless the old name is the agreed contract.
- Audit every template after a model refactor, not only the one that failed; they share field references.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_97Ub_-_Usp4-QW_Kfcu5xg