Troubleshooting and support
When a task fails or produces an unexpected result, identify the point where the work diverged from your request. Start with the account, source, permissions and intended outcome.
Common situations
| Situation | What to check |
|---|---|
| Milo cannot find a record | The correct account is connected, the record is accessible and the request identifies it clearly. |
| An action is unavailable | The connection includes the required permission and the tool is enabled for your account. |
| The answer uses old information | The source date and whether a newer record changes the conclusion. |
| A task stops partway through | Missing input, required approval, provider access or account usage. |
| A submission has no clear result | The destination record or confirmation before retrying. |
An absent response does not establish that an external action failed. Check before repeating anything that might send twice or create a duplicate.
Give a useful correction
The answer used the earlier project plan. Use the revision dated Monday, keep the approval condition from the operations decision, and show what changed in the conclusion.
If the issue is missing access, resolve the connection or provide an authorized source. Repeating the same request without changing the missing prerequisite may produce the same gap.
Contact support
For Milo support, email [email protected]. Include the account email, approximate time and time zone, app or browser, task goal, expected result and what happened instead.
Share only the information needed to investigate. Exclude passwords, access tokens, full payment details and unrelated private records. For enterprise implementation questions, contact the Hexagon team.