Ahhhh! I see a pattern, which starts to make sense for me. The first ever event log with the error mentioned above is on the 14th of july 2021. Two days after you’ve updated the sg-python-api to v3.3.1
Looking at my dev environment I see, that I’ve pulled the v3.3.1 on 14th of july…
So, is there a “one more thing” that was broken in the period of forced migration? Like here?
