no problem also read this topic:
apparently there were some issues with special fields add-on and I think they’re fixed now:
so, maybe update your special fields add-on (if there is an update) to stop this error