Calendar conflict detector
Use “Calendar conflict detector” in Recued. Find double-bookings: every pair of confirmed events in the next N days whose times actually overlap, compared exactly rather than bucketed. Returns a summary, a table of each clashing event with what it clashes against, and the raw pairs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (24 steps)
today_window
date_period
Apply date_period
today_start_ms
date_parse
Parse today window start as a date
today_end_ms
date_parse
Parse today window end as a date
horizon_end_ms
math
Calculate: {{step.today_end_ms}} + {{config.horizon_days}} * 86400000
events_raw
?
events
default
Apply default
scanned_count
count
Count items in events
timed_events
filter
Filter by condition
candidates
ternary
Apply ternary
candidate_count
count
Count items in candidates
overlaps
filter
Filter by condition
overlap_rows
map
Extract from each item
overlap_rows_counted
map
Extract clashes from each item
conflicted
filter
Filter by condition
conflicted_sorted
sort
Sort by
conflicted_rows
slice
Take a subset of
conflict_count
count
Count items in conflicted
has_conflicts
compare
Check if conflict count is greater than 0
conflict_table_starts_text_dated
map
Extract start_at from each item
conflict_table_ends_text_dated
map
Extract end_at from each item
conflict_table
to_table
Format results as a data table
truncation_note
ternary
Apply ternary
all_day_note
ternary
Apply ternary
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
row limit
setting
=
25
scan limit
setting
=
200
horizon days
setting
=
7
calendar slug
setting
=
primary
include all day
setting
=
false
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.