Thank you for contacting us and I'd be happy to assist.
I was able to reproduce this issue on my test website, which happens when a generic field's slug contains an apostrophe character.
These findings have been shared with the concerned team and I appreciate you brought this forward. I'll keep you updated on the progress through this ticket.
For now, a workaround can be to use "&-#-3-9-;" which is the HTML entity number equivalent of an apostrophe character in the field's slug.
( ref: hidden link - please ignore and remove the "-" characters in the entity number as they are added to avoid the conversion )
For example, currently, the slug is:
And you can update it to:
I hope this helps and please let me know if you need any further assistance around this.