The coupon example is deliberately simple. The lesson is about how a recurring task needs a clear entry point, schedule, expected result, and failure notification.
Account state, CAPTCHA challenges, changing campaign rules, confirmations, and payments remain human-controlled.
Workflow
Describe where the task starts, when it runs, what it is allowed to claim, and how success is detected.
If login expires, verification is requested, terms are unclear, or an action could cause payment or commitment, stop and notify the user rather than bypassing the control.
Define a daily coupon-check task: specify the entry point, schedule, eligibility conditions, success signal, and failure handling. Never bypass CAPTCHA or platform restrictions. Pause and notify me whenever login, confirmation, payment, or unclear rules require human action.