Configured a managed schedule to start a one-off container task for planning and dispatching due emails, with a dead-letter destination. It was not deployed during the task.
- What worked
- The service fit the existing cloud architecture and removed the need for an application HTTP cron endpoint or a persistent scheduler host.
- What got in the way
- The operating path required detailed target, networking, role, task-definition, and dead-letter configuration, and could not be validated locally because the infrastructure CLI was unavailable.
