Issue with 3.1.8+

So for some time now we have been stuck using 3.1.7 and have disabled auto updates becaus on any version later than this we see that the process to generate pages will hit like 37/37 then freeze up.

There are over 100 pages but anyway 3.1.7 works fine but we wanted to get this updated so we know its having any other problems looked, I looked into the error logs and can see this happening:

[2024-09-06 14:33:41] qa.ERROR: file_put_contents(/app/simply-static/build/simply-static-1-1725633217//feed/index.html): Failed to open stream: No such file or directory {"userId":1,"exception":"[object] (ErrorException(code: 0): file_put_contents(/app/simply-static/build/simply-static-1-1725633217//feed/index.html): Failed to open stream: No such file or directory at /app/web/app/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php:379)
[stacktrace]
#0 [internal function]: Illuminate\\Foundation\\Bootstrap\\HandleExceptions->handleError()
#1 /app/web/app/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php(379): file_put_contents()
#2 /app/web/app/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php(133): Simply_Static\\Fetch_Urls_Task->add_feed_redirect()
#3 /app/web/app/plugins/simply-static/src/class-ss-archive-creation-job.php(154): Simply_Static\\Fetch_Urls_Task->perform()
#4 /app/web/app/plugins/simply-static/vendor/a5hleyrich/wp-background-processing/classes/wp-background-process.php(531): Simply_Static\\Archive_Creation_Job->task()
#5 /app/web/app/plugins/simply-static/vendor/a5hleyrich/wp-background-processing/classes/wp-background-process.php(350): WP_Background_Process->handle()
#6 /app/web/wp/wp-includes/class-wp-hook.php(324): WP_Background_Process->maybe_handle()
#7 /app/web/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#8 /app/web/wp/wp-includes/plugin.php(517): WP_Hook->do_action()
#9 /app/web/wp/wp-admin/admin-ajax.php(192): do_action()
#10 {main}
"} 

None of the settings have been altered between 3.1.7 and 3.1.8.1 and this isn’t an error we get on that version, the place this is deployed to creates the directory we output to on deployment so it should not be a permissions issue unless you added some more requirement there after 3.1.7?

Can someone help me debug this? I would like to get updated so if there is any more info I can give about this please ask.