Hey all,
Thanks for the reports! It looks like our team is collecting information on this error. If you have already posted then your information is on the tracking! If you have not posted, please reply to this post so I can add you.
EDIT: Update on this! We have enough example cases and QA/Dev has a fix in the works. I don’t have any ETA for when it’ll be available but hopefully it won’t be long.
Thanks for following up with us on this!
Update #2: Latest update with workarounds here