Hello again @eitanc !
Thank you for your patience, and sorry for the inconvenience caused earlier.
I’ve thoroughly reviewed the issue again and attempted to reproduce the problem in our testing environments. While I was able to replicate it, I also noticed several fatal errors originating from the BackWPup plugin, which might be contributing to this issue. This indicates that the problem might be more complex than initially anticipated.
Here’s an excerpt of the errors encountered during testing, which occurred every time a job runs:
[08-Jan-2025 09:11:17 UTC] PHP Fatal error: Uncaught Error: Call to undefined function putenv() in /home/tepiniyopu5661/web/xxx/public_html/wp-content/plugins/backwpup/inc/class-job.php:1600
thrown in /home/tepiniyopu5661/web/xxx/public_html/wp-content/plugins/backwpup/inc/class-job.php on line 1600
I will also post these details on the BackWPup support forum to engage their team and hopefully receive further assistance.
Additionally, I noticed in the original ticket you referenced that other users have reported similar issues despite not having WP Activity Log installed. This strengthens the likelihood that this issue is not directly related to our plugin, but rather an inconsistent problem involving BackWPup itself, or maybe some specific cron job setups.
I plan to respond on the original ticket to provide more visibility for their developers, but in the meantime, have you tried any of the workarounds suggested by their support team? Here are two potential approaches they provided in similar cases (both grabbed from the original ticket):
Let me know if you’ve already tried these or if further assistance is needed from my side. I’ll continue to monitor and provide updates as soon as I hear back from their team.
LATER EDIT / UPDATE:
– the fatal error above was due to my testing environment setup and I was able to solve it (was unrelated)
– I was unable to reproduce the issue again after following a few suggestions from users related to cron job setup (see original thread for more details). I suspect that the actual cron job settings/setup of the site might be the “culprit” here, however, let’s see if there are any updates from their team on this, since multiple other users are experiencing this, in various other contexts, unrelated to WP Activity Log.
Best regards,