Hi @BigBand @zaqwsx3!
We’ve addressed this error message in our latest release. Please update to 3.0.28 and let me know if this persists.
