Cause: The runtime did not call configureEmailsClient(...) before the flow ran.
Check:
- the runner creates the client
- the runner configures it before flow execution
Check:
- whether the flow should pass
after: new Date()
- whether the same inbox is being reused across multiple steps or retries
No Message Arrives Before Timeout
Check:
- the product under test actually sent the email
- the address being used is allowed for the workspace
- the timeout is long enough for the expected delivery path
Where possible, use new: true to generate a unique address for each run. This ensures waitForMessage only sees messages from the current run.
If you must reuse a stable address, pass after: new Date() immediately before the action that triggers the email:
If neither option is available and you are running a local harness, call resetEmailsClient() between test suites to clear the client state. Last modified on June 1, 2026