Manually running a Litmos assign rule is throwing an Oops Error

Manually running a Litmos Assign rule returns an Oops error when a User custom field value type mismatches its defined type. Check User custom fields, run a People Quick report, and update any values so they match the custom field type (e.g. convert string to number). Questions this answers: Why do I get an Oops error when running an assign rule? How do I find the custom field value causing the assign rule error?