We had a bug on our side writing the NaN which we did fix.
To get past the issue while it was fixed (and all events queued up), we had to use a ‘project’ on that trigger to exclude the field.
We weren’t using it in our handling of the response anyway so it was safe workaround.
It would be great to have another option though.
Chris