We haven’t been able to reproduce this one - are you able to point us to a minimal app that demonstrates the problem, or direct us to the actual app with the issue (a /new-build/apps/... link is fine) and tell us how to trigger the exception ourselves?
we can’t reproduce the issue anymore since, all I know is that it works since we have changed the data tables to which the environment points. Since then it works fine.
Strange things happening sometimes but i guess it was some kind of issue when adding environments and chaning databases.
I’ve sent you a link to a session with one of the bugs but i guess without a way to reproduce it this wont be of much use.
Thanks for checking up!
Thanks very much for sending over the additional information. Please let us know if you see the issue again and we’ll start digging and work out what’s going on!