Review missing attachments before sending invitations

User intention

Prepare an invitation email for my survey participants.

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

Compare the attachment problem in the invitation template with the visible invitation preparation form.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Follow the configured attachment problem into invitation preparation and inspect its warning and template link.

How is it judged?

01 · Given

Restore the data and starting state.

An administrator is editing the English invitation template for the active Community feedback survey. The template references participant-guide.pdf, which is absent from the survey upload directory. The template editor shows an attachment error and a missing-file marker. Alex Morgan is an eligible participant with an access code and no invitation sent.

02 · When

Perform the interaction.

The administrator follows the same survey's Participants link, then chooses Invite & remind > Send email invitation to open the invitation preparation form.

03 · Judge

Rationale: Invitation attachments come from a survey's language-specific email template. The administrator needs to know about an unavailable attachment when deciding to send, so recipients are not unknowingly sent an incomplete invitation.

Require

Before Send invitations is chosen, show a visible warning in invitation preparation that a configured attachment is missing or unavailable. Identify the affected file or template sufficiently for review; discovering the problem must not require returning to the template editor.

Allowed

An inline warning, banner, or visible dialog can communicate the attachment problem.
Wording, color, layout, and navigation mechanics may differ while preserving the warning's meaning and timing.
The warning may identify the missing file directly or identify the affected language/template and offer a way to inspect it.
Sending may remain available with an explicit warning or be blocked pending correction or an explicit override; this case does not require a particular sending policy.