Pause the noisy schedule from a hotel lobby

A scheduled curl job is firing too often. It's hitting an API that just rate-limited you. The vendor sent an email. You're at an airport.

You open Hoody on your phone and PATCH /api/v1/curl/schedule/{id}/toggle with enabled: false. The schedule is off. The API stops getting hammered. You haven't touched a laptop, a VPN, an SSH session, a CI rollback, or a deploy.

Tomorrow morning, when the rate limit window resets, you toggle it back on. The schedule keeps its config: the cron expression, the request body, the retry count. Nothing was lost; nothing had to be rebuilt.

The same trick works for the schedule that broke because the upstream URL changed, the one running too often, the one someone else set up that you don't fully understand.

Schedule management is one PATCH from any device.