> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/known-issues/known-issue-unable-to-editupdate-the-fields-for-an-existing-promo-code.md).

# Unable to Edit/Update Fields for Existing Promo Code

**Issue:** When trying to edit the fields of an existing promo code, saving the changes throws an error and the field is not updated. *This is for releases below Release 92.*

**Note:** Currently promo code doesn't support space in the name.

<figure><img src="/files/o81Er4hW5vKgOffOAEuN" alt=""><figcaption></figcaption></figure>

**Workaround:** The current workaround is to create a new Promo-code as the editing doesn't work.

**Long-term fix:** This bug will be prioritised for our roadmap. This article will be updated as more information is available.


---

# 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.limio.com/support/known-issues/known-issue-unable-to-editupdate-the-fields-for-an-existing-promo-code.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.