Thanks for the detailed report.
Using your sample file, I was able to isolate the problem.
This was a bug hiding in the way we process custom properties.
I have implemented a quick fix, that should be available later today when I make the 2.14.0 release. I’ll let you know when it’s available and you can pick the update up from Speckle Manager.
For what ever reason, this custom property was triggering a python stack overflow when we try to convert it. Likely because it has some circular reference.
Now, we do have a check to ensure that circular references don’t cause problems. (this is the max_depth variable you are seeing in the logs)
But clearly this protection didn’t actually save us in this case, so I’ve lowered it’s tolerance from 1000 steps to 200.
I’ve just published 2.14.0 of the Blender Connector, which includes a fix for your first issue.
And, with the file you have sent me, I cannot reproduce the second error message.
Please could you try the new 2.14.0 version, and please let me know if any problems persist!