You have sent a question or request and need to pause until a reply arrives. This phase stops the current run after dispatching your emails, then resumes automatically when the next relevant email is received.
1. Your send_emails are dispatched immediately (the question or request you just sent).2. Your write_notes and delete_notes are executed.3. A continuation email is sent to preserve your full working state.4. This run stops.5. When the next email arrives (expected: a reply to what you sent), processing resumes with your working_note and document context restored.
• Make sure send_emails contains the email you are waiting for a reply to.• Write a clear working_note explaining what you sent, what you are waiting for, and what you plan to do when the reply arrives. This is your orientation when you resume.• Include a patience counter if relevant: 'Waiting for reply to X. Patience: 1 of 5. If no reply by continuation 5, proceed with assumption Y.'On resumption, check working_note to understand what you were waiting for.If the incoming email IS the reply you expected: continue with the work.If it is NOT (e.g. a different email arrived first): handle it and re-send the question if needed.
• waiting: task is NOT done; you need external input before you can continue.• complete: task IS done; any further emails from the user start a new task.Do not use waiting as a way to avoid finishing work. Only use it when you genuinelycannot proceed without a reply.
The waiting iteration itself is brief (just finalising send_emails and working_note). Use next_model='mini'.