Thank you for reporting this issue, we have prioritized a fix for the next release.
The issue is caused by an unsupported data type being logged by the erroring step. As a workaround until the fix is available, you can turn off logging for the errant data object. To do so, go to the step settings panel and deselect the "Log" boolean.
Please reply with any questions or continued errors you find.