Fatal error on activation

We are using W3 Total Cache (Pro) on our production site, but have it deactivated on our development site.

When trying to activate the plugin on the development site, we are getting this fatal error:

/var/app/current/wp-admin/includes/class-wp-filesystem-direct.php on line 173 Warning: chmod(): Operation not permitted in /var/app/current/wp-admin/includes/class-wp-filesystem-direct.php on line 173 Fatal error: Uncaught ArgumentCountError: Too few arguments to function WPForms\Admin\Notifications\Notifications::delete(), 1 passed in /var/app/current/wp-includes/class-wp-hook.php on line 308 and exactly 2 expected in /var/app/current/wp-content/plugins/wpforms/src/Admin/Notifications/Notifications.php:434 Stack trace: #0 /var/app/current/wp-includes/class-wp-hook.php(308): WPForms\Admin\Notifications\Notifications->delete() #1 /var/app/current/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #2 /var/app/current/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /var/app/current/wp-content/plugins/w3-total-cache/Util_Activation.php(17): do_action() #4 /var/app/current/wp-content/plugins/w3-total-cache/Util_Activation.php(41): W3TC\Util_Activation::_cleanup() #5 /var/app/current/wp-content/plugins/w3-total-cache/Util_Activation.php(57): W3TC\Util_Activation::_error() #6 /var/app/current/wp-content/plugins/w3-total-cache/Root_AdminActivation.php(72): W3TC\Util_Activation::error_on_exception() #7 /var/app/current/wp-content/plugins/w3-total-cache/Root_Loader.php(157): W3TC\Root_AdminActivation::activate() #8 /var/app/current/wp-includes/class-wp-hook.php(308): W3TC\Root_Loader->activate() #9 /var/app/current/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #10 /var/app/current/wp-includes/plugin.php(517): WP_Hook->do_action() #11 /var/app/current/wp-admin/plugins.php(194): do_action() #12 {main} thrown in /var/app/current/wp-content/plugins/wpforms/src/Admin/Notifications/Notifications.php on line 434

Any ideas? For security purposes the file system has a different user than the webapp so that’s probably why the chmod command is failing. However, the fatal error seems to come from the notification function, not the failure itself.