> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/events/manage-opened-events/withdraw-an-event.md).
# Withdraw an event
If you have an open event and need to make major changes, such as adding line items or changing quantities, you can withdraw the event.
Withdrawn events are moved back to **Draft** status and can be edited like a new event. When you withdraw an event, any existing supplier responses are removed, and participating suppliers are notified that the event has been withdrawn.
After making your changes, you will need to open the event again to invite suppliers to respond. **Withdrawing an event cannot be undone.**
If your event only requires minor changes, you may be able to [edit your event](https://docs.fairmarkit.com/buyers/request-for-quote-rfq/edit-a-request-for-quote-rfq) instead.
> **Note:** Multi-round events cannot be withdrawn.
### Withdraw event
{% stepper %}
{% step %}
From the Events list or the event Details screen, select **Actions > Edit**.\
A confirmation window displays.
{% endstep %}
{% step %}
In **Withdraw reason**, select the reason you need to withdraw the event. This reason is not sent to suppliers.
{% endstep %}
{% step %}
Click **Withdraw RFQ**. The event is moved to Draft status and it is opened on the [create screen](/buyers/request-for-quote-rfq/create-a-request-for-quote.md).
{% endstep %}
{% step %}
Make any necessary changes to your event, and then reopen or archive it.
{% endstep %}
{% endstepper %}
---
# 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://docs.fairmarkit.com/buyers/events/manage-opened-events/withdraw-an-event.md?ask=&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.
