Service Offerings
Support and TAM ticket information
Click Next.
Click Next.
Click Next > Finish.
The system creates the ticket.
Make your ticket titles short and to the point, summing up the nature of the issue and include which websites or environments are affected. This approach allows Acquia to quickly identify and respond to trends if multiple customers are experiencing the same issue. As you enter text in the field, related links may appear underneath the subject field to assist you with solving common problems. Links will open in a new tab.
A good, clear, and complete description helps Acquia respond to your issue speedily and more accurately. with a first response that is more likely to be a useful solution, rather than only a request for additional information. Keep the following tips in mind when you provide your issue description:
Provide the full URLs affected by the issue.
This includes URLs of pages on your website where you see errors listed, Acquia UI URLs, or URLs of third-party services having trouble connecting to your Acquia website. Acquia can trace these full URLs to exactly what code is running and creating the behavior you are seeing. These URLs help determine whether you are having issues on Acquia servers, your Cloud Platform servers, or on your own web servers outside of Cloud Platform. This also shows Acquia, at a glance, when you are talking about a local instance of a website or a public production website. This is an important part of orienting Acquia in these cases.
Describe the context and nature of the problem.
“I see white screens on every page” is more descriptive than “My website is down!”.
Include the ticket numbers of related tickets, when possible.
This enables the Acquia Support team to quickly research related changes.
Where applicable, include the Task ID for any failed tasks.
If your issue involves a failed task while using the Cloud Platform interface or a command-line operation, Acquia can use the Task ID to help identify the type and source of the error and immediately access the corresponding lines in the logs.
Include when the issue occurred (exact time and time zone).
This allows Acquia to more accurately correlate the issue with any errors or abnormalities in your logs. If you are not sure, try to confirm the last time it worked correctly, if ever.
If relevant, attach screenshots or logs.
Include the browser’s URL bar in any screenshots, and the full path of the log file.
List the steps that will reproduce the issue.
Are there any special access or permissions needed, or do any atypical actions need to be taken to reproduce this issue?
Include what you have done to try to resolve the issue yourself.
Did it change the symptoms you experienced at all? If you explain what did not work, you may keep Acquia from trying something you have already tried, which could help you get on a fruitful path more quickly.
Describe anything that was confusing about what happened.
This information can help Acquia figure out what parts of the platform may be confusing you, which can provide future improvements to user experience or documentation that may help straighten out the issue you are having and help other users as well.
Support tickets have an urgency level. The urgency level determines how quickly Acquia Support will respond to the request, but does not impact a ticket’s time-to-resolution. Here’s what the different urgency levels mean:
| Urgency | Description |
|---|---|
| Critical | Your production system is inoperative. Your business operations or productivity are severely impacted with no available workaround, or there is a critical security issue. Critical issues are eligible for 24x7 support for certain Acquia subscriptions. |
| High | Your production system is operating, but the issue is causing significant disruption of your business operations; a workaround is inadequate. |
| Medium | Your system is operating and the issue’s impact on your business operations is moderate to low; a workaround or alternative is available. |
| Low | The issue is a minor inconvenience and does not impact business operations in any significant way; issues with little or no time sensitivity. |
Acquia recommends creating Support tickets as Medium urgency whenever possible, reserving the use of High for exceptional, non-urgent circumstances that require a more immediate response. Use Low urgency for issues Acquia Support can address within the next business day, as this allows Acquia to more quickly respond to other issues which are more time-sensitive. For more information, see Problem definition categories.
The emergency contact fields only appear if Critical is selected as the ticket urgency. Complete these fields by adding the first and last name, email, and phone number of the emergency contact. This is the person Acquia Support will contact to resolve or report updates on the ticket.
After you create a ticket, you will receive a confirmation email. A member of the Acquia Support team, or your TAM, will respond to the ticket and provide assistance as soon as possible, based on the ticket’s urgency and subscription level.
In a few instances, Acquia requests additional information or provide technical recommendations in a response. When this happens, it is important to provide a timely response and ensure a technical resource is available (if the issue requires it) to answer questions or assist in implementing application-related fixes.
You can find any ticket for your application in the Acquia Support ticket center. The ticket center stores two years of ticket history for you to access.
To access a ticket for your application:
Click My Cases.
You can search within your available cases using the search field on this page.
To further refine your ticket search:
Click your ticket number.
You can track the priority of your ticket along with the current status.
After you file your ticket, Acquia will use the Status field to let you know the ticket’s relative state in Acquia’s workflow, based on the following statuses:
| Status | Explanation |
|---|---|
| New | This ticket has been filed and is awaiting a response from Acquia. |
| Working | An Acquia Support engineer or TAM has accepted the ticket and is working on it. |
| Solved | Acquia has provided an answer to the issue or completed the requested task. If you reply to a ticket in this status, the system automatically updates the status to Working. After a solution is provided, the status is updated again to Solved. Note that if a ticket is marked as Solved for 14 days, the status is updated to Closed. |
| Closed | All work on this ticket is completed. For additional discussion in a Closed ticket, file a follow-up ticket. To open a follow-up ticket, open the Closed ticket and click Create follow-up. |
| Your response needed (Pending) | Acquia has responded to your ticket and is awaiting additional information or instructions. If you require further assistance or have any questions, contact the support team to continue resolving the issue. If you no longer need help or the issue is resolved, there is no action required as the ticket will automatically resolve if it remains in Pending status for 10 consecutive days. |
All users on an application are automatically emailed when a new ticket is created. One contact per ticket receives further communication, but all customers on an application can view all tickets for the application.
If you want additional users added to a ticket, update the ticket with the necessary contact information. Acquia Support updates the ticket accordingly.
Users subscribed to Acquia cannot have any type of autoresponder functionality enabled. Autoresponders have the potential to create endless communication loops (in which two or more systems repeatedly send automated emails to one another) which can affect Acquia’s ability to respond in a timely manner regarding your issue. Since many types of systems can use autoresponders, this functionality includes, but is not limited to, the following:
Acquia reserves the right to suspend any user account causing communication loops.
If you have your own ticketing system that is capable of creating tickets by email and you add your ticketing system’s email address as a contact for your subscription, Acquia’s ticketing system may then create reciprocal tickets in your system. This can create a communication loop in which both systems repeatedly send automated emails to one another, which can interfere with Acquia’s ticketing workflow, and may result in responses to tickets being lost or missed. To prevent this from happening, remove your ticketing system’s contact email from your subscription.
When filing a ticket, the ticketing system will require you to choose an existing subscription.
When you file your ticket to create a new one, choose an existing subscription with the same contacts as the ones you want on your new subscription. This will allow Acquia to make sure the appropriate contacts are added to your new subscription.
Ensure you identify any issue that could prevent Acquia from accessing your website for troubleshooting purposes.
For example, the Drupal account created during installation (UID 1) has all permissions by default, so failing to secure the account may result in potential security risks. To protect against this, you may block UID 1 from accessing your website, but doing so could prevent Acquia from accessing your website to troubleshoot issues.
To avoid this problem, without creating a security risk, use one of the following methods:
Service Offerings/home/sitename directory.After closing a ticket, you may receive a brief satisfaction survey to rate your experience as Good or Bad. The survey also includes an opportunity for you to provide a comment regarding the ticket.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Click the question mark icon (?) on the top-right corner of the UI.
The system displays a pop-up menu.
Click Support from the pop-up menu.
The system redirects to Acquia's site.
Choose View Support Tickets or Submit a Support Ticket.
The system redirects you to the Support page. If the system displays a 403 error page, you must log in.
Click Contact Support.
The system redirects you to the Support page.
Do one of the following:
To create a Support or TAM ticket, you must have an Acquia subscription that supports it, and you must not have used all of your provided Support or TAM tickets. For more information, see the Support Users Guide.
To create a ticket:
Sign in to the Cloud Platform user interface, click the Help icon, and then click Submit a Support Ticket.
Alternatively, sign in to the Acquia Help Center.
Click Contact Support or Create Case.
Click Next.
Click Next.
Click Next.
Click Next > Finish.
The system creates the ticket.
Make your ticket titles short and to the point, summing up the nature of the issue and include which websites or environments are affected. This approach allows Acquia to quickly identify and respond to trends if multiple customers are experiencing the same issue. As you enter text in the field, related links may appear underneath the subject field to assist you with solving common problems. Links will open in a new tab.
A good, clear, and complete description helps Acquia respond to your issue speedily and more accurately. with a first response that is more likely to be a useful solution, rather than only a request for additional information. Keep the following tips in mind when you provide your issue description:
Provide the full URLs affected by the issue.
This includes URLs of pages on your website where you see errors listed, Acquia UI URLs, or URLs of third-party services having trouble connecting to your Acquia website. Acquia can trace these full URLs to exactly what code is running and creating the behavior you are seeing. These URLs help determine whether you are having issues on Acquia servers, your Cloud Platform servers, or on your own web servers outside of Cloud Platform. This also shows Acquia, at a glance, when you are talking about a local instance of a website or a public production website. This is an important part of orienting Acquia in these cases.
Describe the context and nature of the problem.
“I see white screens on every page” is more descriptive than “My website is down!”.
Include the ticket numbers of related tickets, when possible.
This enables the Acquia Support team to quickly research related changes.
Where applicable, include the Task ID for any failed tasks.
If your issue involves a failed task while using the Cloud Platform interface or a command-line operation, Acquia can use the Task ID to help identify the type and source of the error and immediately access the corresponding lines in the logs.
Include when the issue occurred (exact time and time zone).
This allows Acquia to more accurately correlate the issue with any errors or abnormalities in your logs. If you are not sure, try to confirm the last time it worked correctly, if ever.
If relevant, attach screenshots or logs.
Include the browser’s URL bar in any screenshots, and the full path of the log file.
Support tickets have an urgency level. The urgency level determines how quickly Acquia Support will respond to the request, but does not impact a ticket’s time-to-resolution. Here’s what the different urgency levels mean:
| Urgency | Description |
|---|---|
| Critical | Your production system is inoperative. Your business operations or productivity are severely impacted with no available workaround, or there is a critical security issue. Critical issues are eligible for 24x7 support for certain Acquia subscriptions. |
| High | Your production system is operating, but the issue is causing significant disruption of your business operations; a workaround is inadequate. |
| Medium | Your system is operating and the issue’s impact on your business operations is moderate to low; a workaround or alternative is available. |
| Low | The issue is a minor inconvenience and does not impact business operations in any significant way; issues with little or no time sensitivity. |
Acquia recommends creating Support tickets as Medium urgency whenever possible, reserving the use of High for exceptional, non-urgent circumstances that require a more immediate response. Use Low urgency for issues Acquia Support can address within the next business day, as this allows Acquia to more quickly respond to other issues which are more time-sensitive. For more information, see Problem definition categories.
The emergency contact fields only appear if Critical is selected as the ticket urgency. Complete these fields by adding the first and last name, email, and phone number of the emergency contact. This is the person Acquia Support will contact to resolve or report updates on the ticket.
After you create a ticket, you will receive a confirmation email. A member of the Acquia Support team, or your TAM, will respond to the ticket and provide assistance as soon as possible, based on the ticket’s urgency and subscription level.
In a few instances, Acquia requests additional information or provide technical recommendations in a response. When this happens, it is important to provide a timely response and ensure a technical resource is available (if the issue requires it) to answer questions or assist in implementing application-related fixes.
You can find any ticket for your application in the Acquia Support ticket center. The ticket center stores two years of ticket history for you to access.
To access a ticket for your application:
Click My Cases.
You can search within your available cases using the search field on this page.
To further refine your ticket search:
Click your ticket number.
You can track the priority of your ticket along with the current status.
After you file your ticket, Acquia will use the Status field to let you know the ticket’s relative state in Acquia’s workflow, based on the following statuses:
| Status | Explanation |
|---|---|
| New | This ticket has been filed and is awaiting a response from Acquia. |
| Working | An Acquia Support engineer or TAM has accepted the ticket and is working on it. |
| Solved | Acquia has provided an answer to the issue or completed the requested task. If you reply to a ticket in this status, the system automatically updates the status to Working. After a solution is provided, the status is updated again to Solved. Note that if a ticket is marked as Solved for 14 days, the status is updated to Closed. |
| Closed | All work on this ticket is completed. For additional discussion in a Closed ticket, file a follow-up ticket. To open a follow-up ticket, open the Closed ticket and click Create follow-up. |
| Your response needed (Pending) | Acquia has responded to your ticket and is awaiting additional information or instructions. If you require further assistance or have any questions, contact the support team to continue resolving the issue. If you no longer need help or the issue is resolved, there is no action required as the ticket will automatically resolve if it remains in Pending status for 10 consecutive days. |
All users on an application are automatically emailed when a new ticket is created. One contact per ticket receives further communication, but all customers on an application can view all tickets for the application.
If you want additional users added to a ticket, update the ticket with the necessary contact information. Acquia Support updates the ticket accordingly.
Users subscribed to Acquia cannot have any type of autoresponder functionality enabled. Autoresponders have the potential to create endless communication loops (in which two or more systems repeatedly send automated emails to one another) which can affect Acquia’s ability to respond in a timely manner regarding your issue. Since many types of systems can use autoresponders, this functionality includes, but is not limited to, the following:
Acquia reserves the right to suspend any user account causing communication loops.
If you have your own ticketing system that is capable of creating tickets by email and you add your ticketing system’s email address as a contact for your subscription, Acquia’s ticketing system may then create reciprocal tickets in your system. This can create a communication loop in which both systems repeatedly send automated emails to one another, which can interfere with Acquia’s ticketing workflow, and may result in responses to tickets being lost or missed. To prevent this from happening, remove your ticketing system’s contact email from your subscription.
When filing a ticket, the ticketing system will require you to choose an existing subscription.
When you file your ticket to create a new one, choose an existing subscription with the same contacts as the ones you want on your new subscription. This will allow Acquia to make sure the appropriate contacts are added to your new subscription.
Ensure you identify any issue that could prevent Acquia from accessing your website for troubleshooting purposes.
For example, the Drupal account created during installation (UID 1) has all permissions by default, so failing to secure the account may result in potential security risks. To protect against this, you may block UID 1 from accessing your website, but doing so could prevent Acquia from accessing your website to troubleshoot issues.
To avoid this problem, without creating a security risk, use one of the following methods:
/home/sitename directory.After closing a ticket, you may receive a brief satisfaction survey to rate your experience as Good or Bad. The survey also includes an opportunity for you to provide a comment regarding the ticket.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
List the steps that will reproduce the issue.
Are there any special access or permissions needed, or do any atypical actions need to be taken to reproduce this issue?
Include what you have done to try to resolve the issue yourself.
Did it change the symptoms you experienced at all? If you explain what did not work, you may keep Acquia from trying something you have already tried, which could help you get on a fruitful path more quickly.
Describe anything that was confusing about what happened.
This information can help Acquia figure out what parts of the platform may be confusing you, which can provide future improvements to user experience or documentation that may help straighten out the issue you are having and help other users as well.