rule_conflict

A create names a collection that already exists with another rule.

Status: HTTP 409 · Data

What happened

A create names a collection that already exists with another rule. A rule changes from the collection's card on the dashboard, not by creating it again; npx gemmein sync reports it as a conflict line.

Read more

• rule_conflict in the error table
• Collections, filters and totals
• Data: what happens if…
• Changelog: when codes were added or removed