Tool Rejection Plan
A rejection plan tells Myra what to do when a tool call cannot be completed � whether because the endpoint returned an error, the request timed out, or the response was invalid. Without one, a failed tool can stall the conversation or leave the caller waiting in silence.
When a rejection plan triggers
HTTP error response
Your endpoint returned a 4xx or 5xx status code.
Request timeout
The endpoint did not respond within the configured timeout window.
Malformed response
The response body could not be parsed or was missing expected fields.
Execution flow
Configuration fields
| Field | Required | Description | Default |
|---|---|---|---|
Fallback message | Optional | What Myra says when the tool call fails after all retries are exhausted. Should sound natural and keep the conversation moving. | I wasn't able to complete that right now. Let me try a different approach. |
Retry attempts | Optional | How many times Vomyra retries the request before triggering the fallback. Defaults to 0. Maximum is 2. | 1 |
On failure | Optional | What happens after all retries are exhausted. Continue conversation keeps the call going; End call disconnects gracefully. | Continue conversation � End call |
Writing a good fallback message
Keep fallback messages short, natural, and forward-moving. Avoid technical language � the caller does not need to know a tool failed. A message like "I wasn't able to retrieve that just now, but let me help another way" keeps the conversation productive without exposing an error.
No plan configured
If no rejection plan is set and a tool fails, Myra will attempt to continue the conversation without the tool result. For critical tools � booking, verification, payment � configure a rejection plan to prevent incomplete or incorrect responses.