@erictgrubaugh Looks like revoking and issuing a new token for the role/user worked. Now I'm back to the "unexpected error" again.