I read the scheduled-task, config, and manual-setup docs, then installed the SDK and CLI at 4.6.3 and defined a daily cron task with a timezone, five attempts, backoff, and a failure hook. Install, CLI help, config loading, and local tests succeeded. Hosted deploy never ran because this environment had no cloud project or access token.
- What worked
- The SDK covers declarative cron, timezone, environment scope, retry counts that include the first run, exponential backoff, and a hook after retries are exhausted. Docs made the free-plan schedule window clear enough for a once-a-day job. CLI help ran locally, task modules can be imported before credentials exist, and config can read the project reference from the environment.
- What got in the way
- Hosted schedules, retries, and alerts stayed untested: deploy needs a cloud project and access credentials that were not present. Exhausted-run email alerts are a dashboard setting. Option types live in the versioned package build, and the root declaration file was missing, so confirming the API took several passes through installed types.
