Submit a Support Request

Last modified: November 11, 2024

Introduction

In order for Mendix Support to pick up and process your support request, it is important to provide the right information. This will speed up the processing of your request and minimize back-and-forth communication between you and Mendix Support. The details below are what Mendix Support needs and uses to process an incident ticket.

For critical production incidents, please contact Mendix Support by phone.

Checking Useful Links Before Submitting a Request

Before submitting a new Mendix Support request, check these resources to make sure your question has not already been answered:

If you cannot find the answer to your question in the Mendix Community or in the Mendix documentation, you can submit a support request. The Mendix Support Portal will walk you through the ticket creation by asking for relevant information based on the type of request.

Submitting a New Request

You can access the Mendix Support Portal at support.mendix.com.

This is the basic information required for a ticket:

A detailed description of the exact error
A detailed description of the action that was performed when the error was received
A description of the desired goal (optional)
The affected app (for more information, see How to Prepare Your App for Support)

To submit a request with Mendix Support, follow these steps:

Click Submit a request in the upper-right corner of the portal.
Select an issue from the drop-down menu:

You can select from the following issues:
- Request for Information – general questions about Mendix
- Incident – if your app is down, or you are experiencing another platform issue
- Standard Change: Request New Licensed Node – please use the Request New App Node app unless you are requesting an SAP Subscription Secret
- Standard Change: Change On-Prem Licensed Node – request a new license key for an existing app (for example, if you have new hardware configuration)
- Standard Change: Off-Board Licensed Node – remove a licensed node or app that you no longer need (applies to all platforms) by creating a request here
- Standard Change: Change Mendix Cloud Container Size – all vertical scaling changes for a container that require downtime (for example, changing memory or database size) can be requested here
- Standard Change: Change Mendix Cloud File Storage – increase or decrease the file storage size
- Standard Change: Change Mendix Cloud URL – change a non-custom Mendix URL (for example, something.mendixcloud.com)
  
  This URL change will apply to all your environments for this app. For example, the production environment will be something.mendixcloud.com and the acceptance environment will be something-accp.mendixcloud.com.
- Standard Change: Assign Mendix Admin – make an existing Mendix user the Mendix Admin
- Standard Change: Request ATS License – obtain a license to use ATS (for more information on this product, see ATS)
- Standard Change: Request APD License – obtain a license to use APD (for more information on this product, see APD)
- Standard Change: Reset Google authenticator – reset the Google authenticator if you are using it for 2FA (for example, when you get a new phone)
- Standard Change – other changes which can be made on the platform, but for which you do not have access
- Non-Standard Change – any other changes not covered by other issues above
Fill in the fields for the issue type you selected, including Priority.
When you select Request for Information or Incident, you then have to select the Related Component for the issue. The correct component will allow Mendix Support to help you more effectively. In some cases, you can also select the Related Sub-Component for your issue. Selecting the related sub-component is not required, but it will allow Mendix Support to help you more quickly and accurately. There are two main options for the related component:
- App – select one of these components when you have issues with designing, developing, building, deploying, or operating one of your own apps built on the Mendix Platform:
  - App - Development – issues/questions regarding developing your app (for example, with your domain model, widgets, or logic)
  - App - Deployment – issues/questions regarding deploying your app (for example, when the app cannot be deployed or will not start)
  - App - Operations – issues/questions regarding running a deployed app (for example, when the app crashes or shows errors in the log)
  - App - Add-on – issues/questions regarding one of the Mendix add-ons (such as ATS, APD, or AQM)
  - App - Security - issues/questions regarding the security of your Mendix app Please read the section Requirements for Security Support Tickets before raising an app security ticket. Following these guidelines ensures that your ticket can be progressed as efficiently as possible.
  - App - Other – any other issues/questions regarding your own app that you are developing on the Mendix Platform
- Developer Platform – select one of these components when you have issues with the Mendix Platform itself:
  - Developer Platform - Account – issues/questions regarding your Mendix account (for example, when you have difficulties creating an account or signing in)
  - Developer Platform - Marketplace - issues/questions regarding the Mendix Marketplace (for example, when you have difficulties uploading new modules to the Marketplace)
  - Developer Platform - Apps – issues/questions regarding Apps (for example, when you cannot create a story or start a Sprint)
  - Developer Platform - Academy – issues/questions regarding the Mendix Academy (for example, when you cannot open a learning path or you cannot find the attachments required for a module)
  - Developer Platform - Forum – issues/questions regarding the Mendix Community (for example, when you cannot create a new question or add an answer)
  - Developer Platform - Cloud Portal – issues/questions regarding deploying in the Mendix Portal (for example, when you cannot view your log files or scale your environment)
  - Developer Platform - Catalog – issues/questions regarding the Catalog (for example, when you have difficulties accessing the Catalog)
  - Developer Platform - Control Center - issues/questions regarding Control Center (for example, when you have difficulties deactivating applications from Control Center)
  - Developer Platform - Support Portal - issues/questions regarding the Support Portal (for example, when you have difficulties creating Support tickets)
  - Developer Platform - Other – any other issues/questions regarding the Mendix Platform itself
- Licensing – select this component when you have issues/questions regarding your Mendix licenses
Make sure all your attachments have finished uploading before clicking Next.

If investigating the documentation and searching the Mendix Community does not help you solve your issue, you can submit the Mendix Support request.

Request Priority

You can select the priority that you feel the request should have. Please note the SLA regulations for this priority.

The priority is based on the combination of impact and urgency:

Impact	Description
High	A high-priority production issue with a high impact on the customer’s business, impacting (almost) all users.
Medium	A production issue with intermediate impact on the customer’s business, impacting a group of users.
Low	A trivial production issue with no impact on the customer’s business.

Urgency	Description
High	The operational functionality is severely disrupted.
Medium	The operational functionality is fairly disrupted.
Low	The operational functionality is hardly disrupted.

You can set the priority to the following levels:

Critical
High
Medium
Low

The ticket priority that Mendix Support validates is based on this matrix:

Providing Attachments and Additional Information

Depending on the type of request, providing attachments and additional information may be helpful. The scenarios below list what additional information should be provided.

Attachments

You can add large attachments such as app files to the request. Please note that Mendix recommends not attaching any files that contain personal identifiable data, credit card information, or other sensitive data.

Attachments added to Mendix Support requests will be automatically deleted after 365 days.

Requirements for Security Support Tickets

If you are reporting a security finding or other security-related issue, for example a warning issued by a scanning tool, please follow these steps to ensure your ticket is dealt with as efficiently as possible.

Ensure you are using one of the following:
- The current major version of Mendix, preferably an MTS minor version as these continue to get security updates.
- The LTS version of a previous major version which has not reached end of support.
If the security finding is in a Marketplace component:
1. Check that it is platform supported—community-supported components are not supported by Mendix support.
2. Ensure the component is up to date.
Review the Frequently Asked Questions - Security document so see if your finding is described there. Follow instructions there for mitigating your finding, including updating and cleaning up Java libraries. If the finding is addressed there as not having any security implications for your app it is unlikely that raising a ticket will give you more information.
If the issue has been reported by a scanning tool, please check that the results are not caused by factors outside the Mendix app (for example, tool settings or network traffic routing issues).
Include the following information:
- A description of the issue found — please submit only one finding per support ticket.
- Where the issue was found — for example, which URL, which Mendix version, the App ID?
- How the issue was found — for example, was it from scanning an app and, if so, which tool was used?
- A copy of an app containing the reported issue — see How To Export A Mendix App Package for instructions on creating an app package.
- An actual exploitation scenario, if possible, including steps showing how to reproduce and exploit a vulnerability.

Mendix Support will only accept security findings for the Mendix platform. This includes the Mendix runtime, any platform-supported components, and Mendix applications provided to support you to design, develop, deploy, and monitor your apps and Mendix applications used for managing your users and resources. Mendix Support will not look into security findings related to our marketing websites.

Cloud Problems and Deployment Issues

Log file (.txt)
Date and time of the incident

Team Server Problems and App Issues

App ID

Studio Pro Problems

Mendix version
Test app (for details, see How To Export A Mendix App Package)
Reproducible steps

Name of the Marketplace component
Mendix version
Test app (for details, see How To Export A Mendix App Package)
Reproducible steps

Not all Marketplace content is compatible with every version of Studio Pro, and not all Marketplace content is supported by Mendix. For more information, see the Marketplace Content Support section in Marketplace Overview.

Mobile Problems

Operating system and version (Android x.x or iOS x.x; for example, Android 6.1)

Browser Problems

Operating System (Windows x or iOS x; for example, Windows 10)
Browser name and version (Chrome x.x, Firefox x.x, IE x.x, or Safari x.x; for example, Chrome 54.0.2840.99)

Overview of Requests

By clicking your name on the upper-right side of the screen, you can select My activities and see all the requests that you have submitted (My requests) as well as all the requests that have been submitted on the apps to which you have access:

On the All requests tab, you can click Follow for an app to be informed of all the changes on requests on that specific app:

Viewing and Updating Tickets

From the overview, you can easily open a specific request, or you can search for a request by using the Search option. Once you have opened a ticket, you can add comments to the ticket assignee or add new attachments.

The ticket can have the following statuses:

Open – the ticket is in the Mendix Support department
Pending – the ticket is awaiting your reply
- You will receive one reminder email before the Mendix Support Portal automatically closes the ticket
- If you reply, the ticket will be automatically set to Open again
On-hold – the ticket has been forwarded to the Mendix second-line support
- You will be informed on the R&D status and the planned version once a response has been received from the second-line
Solved – the ticket has been solved
- If you reply, the ticket will be automatically opened again
- You can close the ticket yourself by checking the box Please consider this request solved
- The ticket will be closed for comments automatically after a set number of days, after which you can create a follow-up ticket

Submitting a Feature Request

On the Mendix Community, Mendix captures ideas and requests from customers and developers in the Mendix community. Each quarter, the Mendix Community is treated as a short-list of the top features that the Mendix community supports via topics with the most upvotes.