Forums
(@walzim)
2 years, 11 months ago
@joostvandevijver Just wanted to say that so far the error does not occur again. But already before the update to 1.6.2. Strange