Answer
Check the module metadata comment on the custom package involved — the dictionary cache system that resolves custom fields to their backing entities relies on that metadata being correct, and an incorrect value there can cause a custom field to silently misbehave after a component rework, even though the custom field's own definition looks fine; verify the expected comment format against your release's development documentation rather than only re-checking the custom field configuration itself.