Connecting an Environment
Approve an agent pairing request to register your environment with DMM Infinity.
When you deploy a Mendix application with the DMM Infinity agent installed, the agent automatically reaches out to the DMM Infinity cloud to initiate pairing. This page explains the pairing flow and how to approve, manage, and troubleshoot environment connections.
How Pairing Works
The pairing process follows a four-step flow:
- Agent deployed — the agent starts inside your Mendix application and sends a pairing request to DMM Infinity.
- Request received — DMM Infinity validates the request and queues it for approval.
- Admin approval — an organisation admin reviews the request in the portal and approves it.
- Connection established — a secure channel is created between the agent and DMM Infinity. The environment appears on the Environments page.
The pairing request expires after 30 minutes. If it is not approved within that window, the agent will automatically send a new request on the next application restart.
Approving a Pairing Request
When a new pairing request arrives, a modal appears in the DMM Infinity portal:
Review agent details
The modal displays the following information about the agent:
- Application name — the name of the Mendix application
- Environment URL — the runtime URL of the deployed application
- Mendix version — the version of the Mendix runtime
- Agent version — the version of the DMM Infinity agent module
Name the environment
Enter a friendly name for this environment, such as "Development", "Acceptance", or "Production". This name is used throughout the portal to identify the environment.
Use consistent naming across your team. A common convention is to use the environment purpose (e.g., "Dev", "ACC", "PRD") followed by the application name.
Approve the pairing
Click the Approve button to complete the pairing. The modal closes and the environment card appears on the Environments page with a Healthy status.
After Pairing
Once an environment is paired, the agent maintains a persistent heartbeat with DMM Infinity. This heartbeat is used to:
- Report the environment health status (Healthy, Unhealthy, or Unknown)
- Provide entity metadata for the pipeline builder (available tables, fields, and relationships)
- Execute pipeline operations when a run is triggered
Connecting Multiple Environments
You need at least two connected environments to create a pipeline (one source and one target). Repeat the installation and pairing process for each environment you want to connect.
Source and target environments must be on the same platform. Both must be Mendix environments — you cannot mix platforms within a single pipeline.
There is no limit to the number of environments you can connect to a single organisation. Common setups include:
- Development → Acceptance (refresh test data)
- Production → Development (seed local environments with real data)
- Production → Acceptance (replicate production issues)
Troubleshooting
Pairing modal does not appear
If you do not see the pairing modal after deploying the agent:
- Ensure you are signed in to the correct organisation in the DMM Infinity portal.
- Check the Dashboard for a pending notification — the modal may have been dismissed.
- Verify the agent configuration: the Site URL must match the portal URL exactly.
- Check the environment's network connectivity — outbound HTTPS to app.dmminfinity.com must be allowed.
Pairing fails with an error
If the pairing request is rejected or fails:
- Check the error message in the modal for specific details.
- Ensure the agent module is the latest version — older agents may be incompatible.
- Verify that the organisation has not reached its environment limit for the current plan.
- Try restarting the Mendix application to trigger a fresh pairing request.
Environment shows Unknown health
An Unknown status means DMM Infinity has not received a heartbeat from the agent recently:
- Check that the Mendix application is running and has not been stopped or suspended.
- Verify network connectivity — firewalls or proxy changes may be blocking the heartbeat.
- Review the Mendix application logs for errors from the DMMInfinityAgent module.
- If the application was redeployed, the agent may need a few moments to re-establish the connection.