Back
Enum causing 500 Internal Server Error
This was a hard one to hunt down! I first noticed this happened via API and spent like two hours trying to figure out what I was going wrong with my code. But it turns out this error even happens in the web UI.
No idea what the problem is here. Happens when I select a specific one of these enums. The rest work fine
TL;DR
The user is experiencing a 500 Internal Server Error when selecting a specific enum option. This issue occurs both in the API and web UI. The user has tried deleting and re-adding the enum options, but the problem persists. There is an existing issue on GitHub related to this problem. The suggested solution is to monitor the GitHub page for updates.It happens for any new status enums I create. However the original three work, even if I delete them and add them again.
Steps to reproduce:
- Create a new enum with two options: "one" and "two".
- Add a third option, "three"
- Selecting "three" will cause the Server Error
Looks like there is already an issue for this: https://github.com/appwrite/appwrite/issues/5595
Hi @Wintermutation our team is working on it. I would suggest you to keep an eye out on GitHub, since that is where you can see the updates.
