Managing Environments
View, search, and monitor your connected environments.
The Environments page is your central hub for monitoring all connected environments. From here you can view health status, search and sort environments, access detailed information, and test connectivity.
Viewing Environments
Each connected environment is displayed as a card with the following fields:
- Name — the friendly name you assigned during pairing
- Application — the Mendix application name
- URL — the runtime URL of the environment
- Platform — the low-code platform (e.g., Mendix)
- Health status — current connectivity status (Healthy, Unhealthy, or Unknown)
- Last heartbeat — timestamp of the most recent agent heartbeat
- Agent version — the version of the DMM Infinity agent installed
Health Status
DMM Infinity continuously monitors the health of each connected environment via agent heartbeats:
| Status | Indicator | Meaning |
|---|---|---|
| Healthy | Green | The agent is running and responding to heartbeats within the expected interval. |
| Unhealthy | Red | The agent has missed multiple consecutive heartbeats. The environment may be down or experiencing network issues. |
| Unknown | Grey | No heartbeat has been received yet, or the agent was recently deployed and has not checked in. |
Health checks run every 60 seconds. An environment is marked Unhealthy after three consecutive missed heartbeats (approximately 3 minutes of no response).
Searching and Sorting
Use the search bar at the top of the Environments page to filter environments by name, application name, or URL. The search is case-insensitive and updates results in real time.
You can sort environments by:
- Name (alphabetical)
- Health status (Healthy first, then Unhealthy, then Unknown)
- Last heartbeat (most recent first)
- Date added (newest first)
Viewing Environment Details
Click on an environment card to open the detail view. This page provides:
- Full configuration details (Site URL, agent version, Mendix version)
- Heartbeat history — a timeline of recent heartbeat events
- Entity metadata — the list of database entities (tables) available for pipelines
- Pipeline associations — which pipelines use this environment as source or target
- Audit log — recent actions performed on or by this environment
Testing Connectivity
You can manually trigger a connectivity test from the environment detail view:
- Open the environment detail page.
- Click the Test Connectivity button.
- DMM Infinity sends a test ping to the agent and waits for a response.
- The result is displayed immediately — either "Connection successful" or an error message with details.
Use the connectivity test after any network changes (firewall rules, proxy updates, DNS changes) to confirm the agent can still communicate with DMM Infinity.
Troubleshooting
Environment stuck in Unhealthy status
If an environment remains Unhealthy for an extended period:
- Verify the Mendix application is running — check the Mendix Cloud portal or your deployment platform.
- Check for recent deployments — a deployment without the agent module will break the heartbeat.
- Review network settings — ensure outbound HTTPS to app.dmminfinity.com is still allowed.
- Use the Test Connectivity button to get a detailed error message.
Entities not appearing in the pipeline builder
If the pipeline builder does not show entities for an environment:
- Ensure the environment is in Healthy status — entity metadata is only available from healthy agents.
- Wait a few minutes after pairing — the initial metadata sync can take up to 60 seconds.
- Check that the Mendix application has persistable entities — non-persistable entities are not included.
- Redeploy the application if you recently added new entities to the domain model.