Automated backup failure due to Error 408 (Request Timeout)
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- We have identified an incident where a backup failure may occur on automated backups due to an Error 408 (Request Timeout), and subsequent automated retries may result in an error indicating "Your client has taken too long to issue its request."
Resolution
- This error may be appearing due to a large number of backup requests occurring around the same time. If you encounter this behavior, please try starting a manual backup at a later time.
- As a long-term workaround, please consider check the scheduled job's timing, and adjust the cron expression in Backups > Configurations. For example, if your schedule is set to run at 0:15 GMT (e.g., 15 0 * * *) try changing it to execute 30 minutes later at 0:45 GMT (e.g., 45 0 * * *) or a different time preference when activities will be fewer in your region.
Did this article resolve your issue ?