When updating a Feature via API PATCH, get error 400: Cannot update feature with id ####. Value for ownerId is invalid.
This is not happening for all owners, however we can reproduce it for a large number of users in an internal instance.
All of these owners are selectable in the UI and there's no obvious difference between users that produce the error and users that are fine.
- Create a feature
- Try to change its description via PATCH API request and observe the results
- If the operation succeeds, try changing the owner in the UI
If a field can be changed in UI without changing the owner, we should be able to do the same operation via API.
Error 400: Cannot update feature with id ####. Value for ownerId is invalid.
Currently, there is no known workaround for this behavior. A workaround will be added here when available.