> For the complete documentation index, see [llms.txt](https://wiki.zephyr-sim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.zephyr-sim.com/certifications/reviewing-a-certification/email-events.md). # Email Events ## Certification Attempt Submitted - Virtual BPERP Certification When a pilot submits an attempt that needs to be reviewed. APSA receives a notification email and must assign a Reviewer to review the certification. ## Certification Status Update - Virtual BPERP Certification {STATUS} Where STATUS: * REVIEWING * APPROVED * DENIED * AWAITING\_REATTEMPT ### NOTES: {% hint style="info" %} Typically, if no reattempts are prompted, the email flow will go: Attempt Submitted -> Status Update -> REVIEWING -> Status Update -> APPROVED {% endhint %} {% hint style="info" %} If reattempts are prompted, any number of Status Update emails can occur. It might look something like this Attempt Submitted -> Status Update -> REVIEWING -> Status Update - AWAITING\_REATTEMPT -> Attempt Submitted -> Status Update -> APPROVED {% endhint %} ## Certification Attempt Submitted - Virtual BPERP Certification If you allowed a Reattempt, you will be bcc’d on the email that’s sent when the pilot submits their reattempt. This is to let you know that the reattempt was submitted and is ready to be reviewed. --- # 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://wiki.zephyr-sim.com/certifications/reviewing-a-certification/email-events.md?ask=&goal= ``` `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.