Unable to Create New Fields After Renaming to a Previously Disabled Field Name
Hey team,
Thanks for the great work on this project!
We've encountered an issue where creating new custom fields has stopped working, seemingly after a specific sequence of field renaming operations. We suspect this is related to reusing a previously disabled field name.
Steps to Reproduce:
01 - Created a custom field named 'startedFollowingAt' (text type).
02 - Disabled the 'startedFollowingAt' field.
03 - Created a new field named 'socialMediaStartedFollowingAt' (date type).
04 - Attempted to rename 'socialMediaStartedFollowingAt' to 'startedFollowingAt'. This operation failed with an error indicating the name was already in use, even though the original 'startedFollowingAt' was disabled.
Observed Behavior:
After step 4, we are now unable to create or update any new custom fields.
Additional Context:
We've tried clearing the Redis cache, but this did not resolve the issue.
We're unsure if the Redis cache clear contributed to the problem or if it's an independent factor.
Has anyone encountered a similar issue or have any insights on how to diagnose or resolve this? Any help would be greatly appreciated!
Thanks for the great work on this project!
We've encountered an issue where creating new custom fields has stopped working, seemingly after a specific sequence of field renaming operations. We suspect this is related to reusing a previously disabled field name.
Steps to Reproduce:
01 - Created a custom field named 'startedFollowingAt' (text type).
02 - Disabled the 'startedFollowingAt' field.
03 - Created a new field named 'socialMediaStartedFollowingAt' (date type).
04 - Attempted to rename 'socialMediaStartedFollowingAt' to 'startedFollowingAt'. This operation failed with an error indicating the name was already in use, even though the original 'startedFollowingAt' was disabled.
Observed Behavior:
After step 4, we are now unable to create or update any new custom fields.
Additional Context:
We've tried clearing the Redis cache, but this did not resolve the issue.
We're unsure if the Redis cache clear contributed to the problem or if it's an independent factor.
Has anyone encountered a similar issue or have any insights on how to diagnose or resolve this? Any help would be greatly appreciated!
