@tredstone7623 which version of the core are you using now? I think moving to the latest nodejs version probably might have not fixed that above error