Forums
(@pkroh)
9 years, 4 months ago
Because it occurs after the automatic update made by Shield. All previous updates worked well. The database itself is also working fine.