Cloud Platform
Viewing tasks
The Task Log on the Environments page lists all tasks performed on each of your environments during the last seven days. By viewing recent completed tasks, you can diagnose which changes may have caused behavior (good or bad) you are seeing on your website. For each task, the Task Log displays the status, a description, and the start date and time.
For any task, you can click the down arrow to see details of the task. The details include a task ID, user ID, start time, completion time, status, and log entry.
For tasks initiated in the Cloud Platform interface, the user ID displayed is the ID of the logged-in Acquia user. For code commits, the user ID displayed is vcs.commit. For Drush Cloud commands, the user ID displayed is the Unix user that runs the command.
Completed tasks are assigned one of the following states:
The task list includes entries for Stopped or Terminated tasks that you can use to find discover which user requested the action. For these tasks, diagnostic details may appear in the middle of the log output rather than at the end.
The following table lists common messages that may appear in task logs, what they mean, and the recommended action to take.
| Task log message | What it means | Suggested action |
|---|---|---|
| Timed out waiting for the environment (glossary term, activate to view definition) to be switched to the new code |
| During a code deploy, an internal issue may prevent the process from completing. This timeout can occur up to 3 times, and each time the platform will automatically retry the operation. |
| Wait for the task to complete on its own — the platform retries automatically up to 3 times. If the final status is Completed, the code deploy succeeded. If the final status is Failed, you can either retry the code deploy for that environment, or contact Acquia Support and include the task ID shown in the logs along with a note about the timeout error. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
| During a code deploy, an internal issue may prevent the process from completing. This timeout can occur up to 3 times, and each time the platform will automatically retry the operation. |
| Wait for the task to complete on its own — the platform retries automatically up to 3 times. If the final status is Completed, the code deploy succeeded. If the final status is Failed, you can either retry the code deploy for that environment, or contact Acquia Support and include the task ID shown in the logs along with a note about the timeout error. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform