René's URL Explorer Experiment

Title: docs(playbooks): data quality checks, business alerts and self-delivering reports by jamesbhobbs · Pull Request #625 · deepnote/deepnote · GitHub

Open Graph Title: docs(playbooks): data quality checks, business alerts and self-delivering reports by jamesbhobbs · Pull Request #625 · deepnote/deepnote

X Title: docs(playbooks): data quality checks, business alerts and self-delivering reports by jamesbhobbs · Pull Request #625 · deepnote/deepnote

Description: Fifth of five independent playbook PRs: use-case pages that show how existing Deepnote features combine. Every behavioural claim was checked against the source of the currently deployed web app and the CLI in this repository. Pages docs/playbook-data-quality-checks.md: one checks notebook that runs in CI on pull requests with deepnote run and on a schedule in Deepnote Cloud, with alerts, auto-pause and snapshots. docs/playbook-business-alerts.md: two ways to alert on business conditions, by raising for schedule notifications or by posting a message from the notebook, and when to use each. docs/playbook-reports-that-deliver-themselves.md: a scheduled report that updates its app and embeds, notifies readers, keeps an archive and shows readership. Fix to an existing page docs/scheduling.md said hourly and custom schedules were Enterprise-only. In the deployed code, hourly and custom cron schedules are on Team. Only schedules that run more often than once an hour need Enterprise; the server rejects them otherwise. Claims checked against source Schedule notifications are Slack or email, on success and/or failure. Messages contain a fixed sentence and a link, plus an app link in email when the scheduled notebook is the published app. Errors and outputs aren't included. Email recipients are workspace members. Auto-pause is per schedule. New schedules in the UI default to on with 3 consecutive failures, and the effective threshold is never less than about one hour of runs. Update notebook with run results controls both write-back and app republishing. Snapshot retention is 1 day on Free, 30 days on Team and 365 days on Enterprise. Agent blocks are enabled by default whenever AI is enabled, and the agent's summary is written back after scheduled runs. CLI behaviour, from this repository: deepnote run exits 1 on a failing block and reports failureCategory. It loads .deepnote.env.yaml from the working directory and resolves env: references, with real environment variables taking precedence over .env. deepnote integrations pull exists. The workflow YAML and Python snippets parse. They haven't been run. Not verified Running the GitHub Actions example against a real warehouse. Rendering on the docs site, and the "Playbooks" sidebar section, which will come in a separate docs-navigation PR. 🤖 Generated with Claude Code Summary by CodeRabbit Documentation Added playbooks for creating business alerts, running data-quality checks in CI and on a schedule, and distributing recurring reports. The playbooks cover alert delivery options, notebook checks, scheduled runs, notifications, report sharing, snapshots, and plan requirements. Added “EMEA” to the documentation dictionary. Updated scheduling plan information: scheduling is available on Team and Enterprise plans; schedules running more often than hourly remain Enterprise-only.

Open Graph Description: Fifth of five independent playbook PRs: use-case pages that show how existing Deepnote features combine. Every behavioural claim was checked against the source of the currently deployed web app and...

X Description: Fifth of five independent playbook PRs: use-case pages that show how existing Deepnote features combine. Every behavioural claim was checked against the source of the currently deployed web app and...

Opengraph URL: https://github.com/deepnote/deepnote/pull/625

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width