Provider Reply Failures
Provider reply failure means AxiOwl may have sent a message, but the target did not reply over AxiOwl MCP.
Failure Types
| Failure | Meaning |
|---|---|
| No provider receive proof | Delivery path may have failed. |
| Provider received but no MCP tools | Provider config/startup problem. |
| Provider replies manually but not through MCP | Tool availability or instruction problem. |
| Provider replies with wrong sender | Metadata or registry problem. |
| Provider replies from old chat | Discovery/targeting problem. |
Questions To Ask
- Did AxiOwl return
accepted_by_axiowl? - Did provider edge report
accepted_by_provider? - Did the provider UI/session show the message?
- Did the provider have AxiOwl MCP tools?
- Did the provider call
axiowl_send_message? - Did the MCP call include provider metadata?
- Did AxiOwl resolve sender identity correctly?
Good Test Prompt
AxiOwl provider response test. Please respond over AxiOwl MCP with your current status and include: AXIOWL_TEST_OK <run-id>
This gives the investigator a stable phrase and run id.