Thanks for the report. I think this was a bug in the published event that I fixed after it was published, so that reply will always be broken. But if you see behavior like this again please let me know!