@ABLPHA Could you please upgrade to the latest version (3.1) and check if the issue persists?