E.g. try to use the servicedesk request field in a smart-value when the user who triggered the issue event was not a servicedesk agent. The request type field will just contain a permission error in the JSON.
Right now the workaround is to refresh the issue in the rule, since that will re-load it as the rule actor.
To fix this properly, maybe we can serialise the issue as the rule actor (though that's not available when we process the event the first time - might have to add some list of known problematic fields to the enricher)