[Resolved] WPML Activation Triggers Excessive Resource Usage Leading to 524 Timeout Error

Background of the issue:
I am trying to activate and configure WPML on our TEST site, which is a copy of the production site at hidden link. Our production site has a large volume of posts, each with many attachments. During activation, WPML processes attachments and translations, triggering heavy SQL queries. Examples of these queries include: SELECT posts.ID, post_meta.post_id, post_meta.meta_key, post_meta.meta_value FROM wp_posts AS posts LEFT JOIN wp_postmeta AS post_meta ON posts.ID = post_meta.post_id AND post_meta.meta_key = 'wpml_media_processed' WHERE posts.post_type = 'attachment' AND (post_meta.meta_value IS NULL OR post_meta.meta_value != 1) LIMIT 300; and INSERT IGNORE INTO wp_icl_translations (`element_type`, `element_id`, `trid`, `language_code`) SELECT CONCAT('post_', p.post_type) as element_type, p.ID as element_id, 28165794 + p.ID as trid, 'es' as language_code FROM wp_posts p LEFT OUTER JOIN wp_icl_translations t ON t.element_id = p.ID AND t.element_type = CONCAT('post_', p.post_type) WHERE p.post_type = 'attachment' AND t.translation_id IS NULL LIMIT 500; These queries are resource-intensive due to our dataset size.

Symptoms:
Activating WPML triggers excessive resource usage, leading to a 524 timeout error.

Questions:
Can WPML prevent running heavy processes during activation?
Is it possible to defer or split these tasks into smaller chunks using WP-Cron or CLI?
Are there filters, constants, or configuration flags to disable or postpone bulk processing?
Does WPML have a recommended approach for handling activation in high-content environments?
Is there dedicated documentation for optimizing or deferring WPML activation processes in high-volume environments?