All exports timeouting

[lpiob]

I have a problem with the (paid version of) SimplyStatic extension.

Despite:

• having full control of the hosting environment,
• having define('DISABLE_WP_CRON', true); and having php wp-cron.php in crontab
• having Use server-side cron job enabled in SimplyStatic setting
• having max_execution_time=0 in CLI PHP.

All our attempts to export content fail due to mod-php max_execution_time being too low.

[2026-03-03 08:31:07] Error: (1) Maximum execution time of 240 seconds exceeded in /var/www/REMOVED/wp-content/plugins/simply-static-pro/vendor/guzzlehttp/psr7/src/Utils.php on line 132
[2026-03-03 08:31:07] Error: (1) Maximum execution time of 240 seconds exceeded in /var/www/REMOVED/wp-content/plugins/simply-static-pro/vendor/guzzlehttp/psr7/src/Utils.php on line 132

I believe that the backend is failing while invoking
/wp-admin/admin-ajax.php?action=wp_archive_creation_job&nonce=REMOVED&chain_id=REMOVED
over localhost

I understand that the site may be large and I don't mind longer export time, but I don't want to increase max_execution to infinity.

How to instruct SimplyStatic to perform these actions backend-side?

[patrickposner]

Hey @lpiob,

I would look into gradually increasing the limits inside Simply Static via the implemented filters:

Fetch Timeout:

add_filter( 'ss_remote_get_args', function( $args ) {
    $args['timeout'] = 120; // 2 minutes per page fetch
    return $args;
} );

Background Process Timeout:

add_filter( 'wp_simply_static_default_time_limit', function( $time ) {
    return 60; // 60 seconds per batch instead of 20
} );

[lpiob]

I've tried all combinations of those limits. Generation process always failed.
I've isolated it to happen during the S3 upload stage.
Do these parameters control that stage?

At the moment I've switched to local storage output and I am executing aws s3 sync manually.