Use “Is my Netlify site actually broken” in Recued. Reports what is live on a Netlify site versus what was merely deployed. It reads information without changing data in the connected service.

How it works 23 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (23 steps)

■ site_id trim

Trim whitespace from setting site id

■ site_required template

Generate text from a template

fail: step.site_id is_empty

■ page clamp

Clamp setting per page between 1 and 100

◆ site_raw recued-core.netlify.site.read

Read site on netlify

■ defaults defaults

Apply defaults

◆ deploys_raw recued-core.netlify.deploy.search

Search deploy on netlify

■ deploys default

Apply default

■ have_deploys template

Generate text from a template

fail: step.deploys is_empty

■ deploy_count count

Count items in deploys

■ production filter

Filter by condition

■ prod_count count

Count items in production

■ previews filter

Filter by condition

■ preview_count count

Count items in previews

■ prod_failed filter

Filter by condition

■ prod_failed_count count

Count items in prod failed

■ preview_failed filter

Filter by condition

■ preview_failed_count count

Count items in preview failed

■ newest_prod find

Find first match in

■ defaults_2 defaults

Apply defaults

■ drifted compare

Check if newest prod id does not equal published id

■ card to_summary

Format results as a summary card

■ failed_table_rows map

Extract from each item

■ failed_table to_table

Format results as a data table

▼

Output

summary card

table failed_table

Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

site id setting =

per page setting = 50