a fix for this should be in an upcoming build
1 Like
Many thanks @mike.maxwell, look forward to it.
I am also getting (I think) the same error.
Is a fix for this still upcoming?
Thanks
its in the 2.3.6 release which is currently in beta.
1 Like
Hiya, ive upgraded both my hubs and am still seeing this error. Should it still be occuring?
huh, i'll try something different here...
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
