> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/help-center/getting-started/integration-and-testing-troubleshooting.md).

# Integration & Testing Troubleshooting

Use these answers to resolve common integration and testing issues.

<details>

<summary>My review-evidence video will not upload</summary>

Review-evidence videos have a 100 MB upload limit. Convert or compress the video to MP4 before uploading.

For longer videos, share the recording with your MDI contact in Slack.

</details>

<details>

<summary>I updated my intake form after approval. Do I need another review?</summary>

Yes. Approval applies only to the version reviewed at that time.

Request approval again if you change the intake form, supporting materials, or treatment plan.

</details>

<details>

<summary>The live pharmacy test is stuck</summary>

The pharmacy must confirm the test order. This step has no fixed completion time.

Contact your pharmacy partner if the test is delayed. Also update your MDI contact in Slack.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/help-center/getting-started/integration-and-testing-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.