Remove the default email recipient while creating a question alert

User intention

Configure email recipients for a saved question's alert.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Watch Send now after the default recipient is removed. The recipient field becomes empty, but Send now remains enabled.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Removing the default recipient immediately disables Send now until a recipient is provided.

How is it judged?

01 · Given

Restore the data and starting state.

The New alert modal is open for a saved question with an Email delivery handler containing the sole default recipient, no configured Slack channel, and Send now available.

02 · When

Perform the interaction.

The person removes the sole email recipient, leaving none of the enabled delivery handlers with a valid destination.

03 · Judge

Rationale: A question alert sends a saved query’s results to its recipients. The recipient list can become empty while the user edits it, leaving no destination for an immediate send. Send now should be unavailable in that state, independently of the schedule settings used to save the alert.

Require

Send now remains unavailable until an enabled delivery handler has a valid destination.

Allowed

The valid target may be an email recipient, a configured Slack channel, or another supported delivery handler. Done may remain unavailable while schedule requirements are incomplete even when Send now becomes available. The disabled styling, explanatory copy, and focus behavior may follow the existing design system.