could it be an access issue related to the custom field? or is it intermittent for the users who do see the error?