When attempting operations that require lengthy processing, a merchant on Adobe Commerce Cloud receives a timeout error after 180 seconds. How would the developer deal with this issue? A. 1. Modify…

Question

Options

• A
  1. Modify admin timeout into .magento.app.yamifile. 2. Commit and push that code from the local environment. 3. Move code to Production environment.
• B
  1. In the Fastly Configuration section > Advanced Configuration. 2. Set the Admin path timeout value in seconds. 3. Save config and Upload VCL to Fastly.
• C
  1. Modify admin timeout into app/etc/config.php file. 2. Commit and push that code from the local environment. 3. Submit a support ticket to apply the changes.

• A
  8% (4)
• B
  76% (38)
• C
  16% (8)

Explanation

The developer can deal with this issue by modifying the admin path timeout value in seconds in the Fastly Configuration section > Advanced Configuration in the Admin Panel. Fastly is a cloud-based caching service that improves site performance and security for Adobe Commerce Cloud projects. Fastly has a default timeout value of 180 seconds for admin requests, which means that any request that takes longer than 180 seconds will be terminated and result in a timeout error. The developer can increase this value to allow longer processing time for admin requests without causing errors. The developer also needs to save the configuration and upload VCL to Fastly to apply the changes. Verified Reference: [Magento 2.4 DevDocs]

No community discussion yet for this question.