# Run a bounded OpenClaw scheduled digest Check scheduler availability in the deployed app, define a narrow source and recipient, then inspect one due run and its delivery. Canonical: https://xcloud.host/use-cases/playbooks/openclaw-scheduled-digest/ Published: 2026-10-01 · Updated: 2026-10-01 · Technical review: 2026-10-01 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Schedule one recurring digest and verify delivery without duplicates For: operations-owner ## Requirements and responsibilities - Confirm that the deployed build exposes OpenClaw automations and the operator has application admin permission. The upstream scheduler depends on a running Gateway; xCloud does not document a dedicated automation panel. Sources: [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron); [Managed OpenClaw Hosting](https://xcloud.host/openclaw-hosting/); [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/) - Choose public sources, one recipient, a time zone and a harmless first run. Sources: [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron); [Managed OpenClaw Hosting](https://xcloud.host/openclaw-hosting/); [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/) ## Illustrative situation Illustrative scenario: an owner wants a weekday digest of two public status pages sent to the approved Telegram account. ## Choose the approach - Use the OpenClaw application scheduler only after finding it in the deployed interface or getting a documented operator handoff. Keep xCloud server cron separate from application-owned automation. Sources: [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron); [Managed OpenClaw Hosting](https://xcloud.host/openclaw-hosting/); [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/) ## Dashboard and application procedure ### 1. Define the digest contract **Where:** Owner runbook **Permissions:** Authorized OpenClaw owner or application administrator **Inputs:** Two public URLs, weekday time, time zone and Telegram recipient **Action:** Specify a two-bullet digest with direct source links, one message to the named Telegram recipient per occurrence, and no other writes. **Expected result:** A bounded job specification exists. **Verify:** Have the recipient confirm source list and local delivery time. **If it fails:** If no owner can identify a missed or duplicate run, do not enable recurrence. Capability: Configure an OpenClaw application behavior Sources: [Managed OpenClaw Hosting](https://xcloud.host/openclaw-hosting/); [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs) ### 2. Verify app scheduler access **Where:** Deployed OpenClaw application **Permissions:** Authorized OpenClaw owner or application administrator **Inputs:** Current automation controls and admin identity **Action:** Have an authorized app administrator verify the Gateway and \`openclaw automations\` availability through the documented xCloud SSH handoff if granted; list existing jobs before changes. Do not assume an xCloud cron UI creates app jobs. **Expected result:** The feature and permission path are known. **Verify:** Locate existing jobs before creating a new one. **If it fails:** If no scheduler surface is available on this hosted build, stop and leave the digest manual. Capability: Configure an OpenClaw application behavior Sources: [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/); [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron) ### 3. Create one named job **Where:** OpenClaw automation control **Permissions:** Authorized OpenClaw owner or application administrator **Inputs:** Unique job name, schedule and destination **Action:** Have the app administrator use the current \`openclaw automations\` create syntax for a recurring isolated job, with the agreed time zone and approved Telegram destination. Permit only the named Telegram delivery; keep source reads public and all other writes out of scope. **Expected result:** One job is listed with the expected schedule and recipient. **Verify:** Compare name, time zone, payload and destination with the runbook. **If it fails:** If a similar job already exists, update or retire it instead of creating a duplicate. Capability: Configure an OpenClaw application behavior Sources: [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/); [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron) ### 4. Inspect one due run **Where:** OpenClaw job history and Telegram **Permissions:** Authorized OpenClaw owner or application administrator **Inputs:** Scheduled occurrence ID or time window **Action:** Wait for a due run or use an authorized test run, then inspect \`openclaw automations runs \\` and compare it with the delivered Telegram message and links. **Expected result:** Exactly one complete digest is delivered for the occurrence. **Verify:** Check run status, recipient, timestamp, two bullets and source links. **If it fails:** If delivery fails or duplicates, pause the job and reconcile history before retrying. Capability: Configure an OpenClaw application behavior Sources: [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/); [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs); [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron) ### 5. Assign failure ownership **Where:** Runbook and application job list **Permissions:** Authorized OpenClaw owner or application administrator **Inputs:** Owner, missed-run threshold and pause path **Action:** Document who checks job history and how to pause or resume after a provider or channel outage. **Expected result:** The job has a named operator and recovery rule. **Verify:** Have the operator locate the job and explain how to detect a duplicate. **If it fails:** If history or pause control is unavailable, treat the schedule as unverified and disable it. Capability: Configure an OpenClaw application behavior Sources: [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/); [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs) ## Maintenance - At each due occurrence, compare one job-history entry with exactly one Telegram message, inspect source links, and flag a missed or duplicate delivery. Sources: [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs) ## Recovery decisions - If a run fails or duplicates, pause the named automation, preserve its job ID and run history, and reconcile which occurrence was delivered before a retry. Resume only after one test run passes. Sources: [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs) ## AI handoff Use the named xCloud dashboard for hosted controls and verify application tools in the deployed OpenClaw version before use. An xCloud hosting MCP write operation for these actions is not documented. ### Supported scope - **Configure an OpenClaw application behavior** (app; manual): Upstream OpenClaw documentation describes application features. xCloud does not document every app configuration surface or pre-enabled tool. Verify the feature and permissions in the deployed build before editing. Checkpoint: Use a harmless positive and negative test; preserve current configuration and stop if the feature is unavailable. Sources: [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/); [OpenClaw security and access control](https://docs.openclaw.ai/help/faq/security-and-access-control) ### Copyable agent brief ```text At the agreed weekday time, read only these two public status pages [URLs]. Send exactly one two-bullet digest with direct links to approved Telegram recipient [ID]. Do not write elsewhere or send if source fetch fails; mark uncertainty. ``` ### Manual checkpoints - An authorized application admin confirms the deployed Gateway and current \`openclaw automations\` CLI before creating the job. - The recipient checks one message against \`openclaw automations runs \\` and pauses duplicates. ## Feature coverage - **task setup and decision** (covered): Defines prerequisites and an explicit hosted/application handoff. Steps: scope, availability - **task acceptance and failure** (covered): One scheduled occurrence produces exactly one linked two-bullet digest to the approved recipient, with a matching run-history entry. Failure: Unavailable scheduler, incorrect time zone, missing history, failed delivery or duplicate delivery blocks recurring use. Steps: draft, observe, handover ## Sources - [OpenClaw automations](https://docs.openclaw.ai/automation/cron-jobs) — reviewed 2026-10-01 - [OpenClaw automation CLI](https://docs.openclaw.ai/cli/cron) — reviewed 2026-10-01 - [Managed OpenClaw Hosting](https://xcloud.host/openclaw-hosting/) — reviewed 2026-10-01 - [How to Deploy OpenClaw with xCloud](https://xcloud.host/docs/how-to-deploy-openclaw-with-xcloud/) — reviewed 2026-10-01 - [OpenClaw security and access control](https://docs.openclaw.ai/help/faq/security-and-access-control) — reviewed 2026-10-01 ## Continue [OpenClaw hosting details](https://xcloud.host/openclaw-hosting/) - [Admit one Telegram sender to hosted OpenClaw](https://xcloud.host/use-cases/playbooks/openclaw-telegram-approved-sender/) - [Triage a silent OpenClaw agent with hosted logs](https://xcloud.host/use-cases/playbooks/openclaw-log-triage/)