Common Errors and Troubleshooting
Troubleshoot type mismatches, empty dates, list-versus-single-value mistakes, dateBetween offsets, and regex escaping errors in Notion formulas.
Use this page to troubleshoot formula errors. Find the closest error type first, then compare your formula with the safer pattern.
Type mismatch
Wrong example:
If Amount is a number, you may need to convert it to text:
Empty date errors
Wrong example:
Safer pattern:
Mixing lists and single values
Person, relation, and multi-select properties often return lists.
Wrong mental model:
More reliable pattern:
If you only want the first item:
dateBetween() is off by one day
If you use now(), the specific time is included in the calculation. If your due date has no time, the result may feel unintuitive.
For task due-date checks, prefer:
Instead of:
Formula depth is too deep
Notion's official error explanation notes that formula depth increases when formulas reference formulas, formulas reference rollups, or rollups reference formulas again. The depth limit is 15 layers.
Ways to fix it:
- Reduce chained references between formulas.
- Split overly long formulas into databases closer to the original data source.
- Avoid passing the same calculated value back and forth between multiple rollups.
- For large systems, use a three-layer structure: raw data -> intermediate metrics -> display results. Do not nest endlessly.
Regex escaping errors
When writing regular expressions inside Notion strings, backslashes usually need to be doubled.
Match numbers:
Match a dot:
Automation return type errors
If an automation needs to fill a date, your formula must return a date, not a text-formatted date.
Wrong example:
Correct direction:
To use these formulas directly in task reminders, project progress, note heatmaps, and reports, continue with FLO.W Notion Template.
Last updated on
Notion Formulas