> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow-ereporting-for-industry/monitor-submission-status.md).

# Monitor Submission status

### Monitoring Submission status

The “Submission status” page shows all submitted reports and their processing status for the past 35 days.

Statuses include:

* **Transmission pending**: waiting for processing; no acknowledgement message yet.
* **Accepted**: successfully processed; all ICSRs accepted.
* **Rejected** or **All rejected**: errors in the submission; see acknowledgement message.
* **Partially Accepted**: some ICSRs accepted, others not; see acknowledgement message.
* **Failed**: submission failure not caused by ICSR content.

You can download the **acknowledgement message** or **submitted XML** from this page.

***

### Interpreting acknowledgement messages <a href="#toc234917184" id="toc234917184"></a>

<details>

<summary>For E2B R3:</summary>

\<acknowledgement typeCode="AA">\[GN3] &#x20;

* AA – Application Acknowledgment Accept (message successfully processed, no further action)
* AE – Application Acknowledgment Error (needs correction)
* AR – Application Acknowledgment Reject (must resend entire transaction)

&#x20;

Error details appear under **\<acknowledgementdetail>**.

If unclear, contact the NRA.

</details>

<details>

<summary>For E2B R2:</summary>

* **01** = Report loaded successfully
* **02** = Report not loaded
  * Error reason appears in <**errormessagecomment**>

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.who-umc.org/vigiflow-ereporting-for-industry/monitor-submission-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.