FAQ & Troubleshooting

Quick answers to the problems people hit most — what went wrong, why, and how to fix it.

• ArticleMy entry does not appear on the siteAlmost always one of three things: the entry is not published, the site was never granted access to that collection, or the site is showing a cached copy. Check the entry's status first — it is the cause in most cases — then the site's per-collection permissions, then caching.
• ArticleMy entry will not saveA refused save is almost always one of five things: a required field left empty, a value outside a field's allowed set, a duplicate in a field that must be unique, a link pointing at something that does not exist, or — for bookings — a slot with no capacity. The message names the field; fix that field rather than retrying.
• ArticleMy automation did not runWork through it in this order: the automation is not active, the trigger is not listening to where your change came from, the trigger does not match what actually happened, a condition stopped the run, or it started and is stuck. The run history tells you which — whether a run exists at all is the first thing to look at.
• ArticleDuplicate value on a unique fieldThe save was refused because another entry in the same collection already holds that value in a field marked unique. Find that entry, then either update it instead of creating a new one, change your value, or archive the old entry if it is no longer needed; archived entries do not count.
• ArticleMy rollup is not recalculatingA rollup recalculates whenever a related entry is saved, so a wrong number almost always means the entries it reads are not the ones you expect: they do not point back at this entry, its filter leaves them out, or the field it totals is empty. Check those three before anything else.