Environment State

Track what’s deployed to each environment across your solutions.

What is Environment State?

Environment state tracks:

• Which solution versions are deployed
• When deployments occurred
• Current health of each environment

┌─────────────────────────────────────────────────────────────┐
│  Environment State: Production                              │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌────────────────────┬─────────┬────────────────────────┐  │
│  │ Solution           │ Version │ Last Deployed          │  │
│  ├────────────────────┼─────────┼────────────────────────┤  │
│  │ customer-portal    │ 1.3.0   │ Today at 14:30         │  │
│  │ auth-service       │ 2.1.0   │ Yesterday              │  │
│  │ payment-gateway    │ 1.0.5   │ 3 days ago             │  │
│  │ notification-svc   │ 0.9.2   │ 1 week ago             │  │
│  └────────────────────┴─────────┴────────────────────────┘  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Viewing Environment State

From Environment Detail

Navigate to an environment to see all deployed solutions:

┌─────────────────────────────────────────────────────────────┐
│  Production                                                 │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Description: Live customer-facing environment              │
│  Targets: 12 (11 online, 1 stale)                           │
│                                                             │
│  ─────────────────────────────────────────────────────────  │
│                                                             │
│  Deployed Solutions:                                        │
│                                                             │
│  ┌────────────────────┬─────────┬────────────┬────────────┐  │
│  │ Solution           │ Version │ State      │ Actions    │  │
│  ├────────────────────┼─────────┼────────────┼────────────┤  │
│  │ customer-portal    │ 1.3.0   │ Deployed   │ [Rollback] │  │
│  │ auth-service       │ 2.1.0   │ Deployed   │ [Rollback] │  │
│  │ payment-gateway    │ 1.0.5   │ Deployed   │ [Rollback] │  │
│  └────────────────────┴─────────┴────────────┴────────────┘  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

From Solution Detail

See where a solution is deployed across environments:

┌─────────────────────────────────────────────────────────────┐
│  customer-portal                                            │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Environment State:                                         │
│                                                             │
│  ┌────────────┬─────────┬────────────────┬───────────────┐ │
│  │Environment │ Version │ Deployed       │ Action        │ │
│  ├────────────┼─────────┼────────────────┼───────────────┤ │
│  │Development │ 1.4.0   │ 1 hour ago     │ [Promote]     │ │
│  │Staging     │ 1.3.0   │ 2 days ago     │ [Promote]     │ │
│  │Production  │ 1.3.0   │ 5 days ago     │ -             │ │
│  └────────────┴─────────┴────────────────┴───────────────┘ │
│                                                             │
└─────────────────────────────────────────────────────────────┘

State Components

Version Tracking

Each solution-environment combination tracks:

Field	Description
Current Version	Active deployed version
Deployed At	When deployment completed
Deployed By	User who initiated deployment
Deployment ID	Reference to deployment record

State Type

Each environment state-history record carries a state_type that describes the action which produced it. The current-state snapshot itself has no state_type, and the current implementation records Deployed for every event — Rolled Back and Promoted are defined but not yet emitted:

State Type	Description
Deployed	A deployment completed successfully
Rolled Back	A rollback was applied to this environment
Promoted	A version was promoted into this environment

State Flow

Version Comparison

Cross-Environment View

The solution detail view shows which version is currently deployed in each environment. You can see at a glance whether the same version is running across Development, Staging, and Production, and initiate a promotion from this view when versions differ.

History Tracking

Deployment History

View historical deployments for an environment:

┌─────────────────────────────────────────────────────────────┐
│  Deployment History: Production                             │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌────────────────┬─────────┬────────────┬───────────────┐ │
│  │ Date           │ Solution│ Version    │ Result        │ │
│  ├────────────────┼─────────┼────────────┼───────────────┤ │
│  │ Today 14:30    │ portal  │ 1.3.0      │ ✓ Success     │ │
│  │ Yesterday      │ auth    │ 2.1.0      │ ✓ Success     │ │
│  │ 3 days ago     │ portal  │ 1.2.0→1.3.0│ ✓ Success     │ │
│  │ 1 week ago     │ payment │ 1.0.5      │ ✓ Success     │ │
│  │ 2 weeks ago    │ portal  │ 1.1.0→1.2.0│ ✓ Success     │ │
│  └────────────────┴─────────┴────────────┴───────────────┘ │
│                                                             │
└─────────────────────────────────────────────────────────────┘

State Snapshots

Point-in-time view of environment state:

┌─────────────────────────────────────────────────────────────┐
│  State Snapshot: Production - 2024-01-15                    │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  As of January 15, 2024:                                    │
│                                                             │
│  customer-portal:  v1.2.0                                   │
│  auth-service:     v2.0.0                                   │
│  payment-gateway:  v1.0.5                                   │
│                                                             │
│  Compare to today:                                          │
│  customer-portal:  v1.2.0 → v1.3.0 (+1)                     │
│  auth-service:     v2.0.0 → v2.1.0 (+1)                     │
│  payment-gateway:  (no change)                              │
│                                                             │
└─────────────────────────────────────────────────────────────┘

State Refresh

Automatic Updates

State updates automatically when:

• Deployment completes
• Promotion occurs
• Rollback executes

Manual Refresh

Environment state is derived from deployment history and updates automatically as deployments complete. The current state for each environment is shown in the Lens environment views; there is no separate manual-refresh command.

Viewing State

Environment state — which solution version is deployed where — is presented in the Lens environment and solution views.

A conceptual view of an environment’s deployed solutions:

{
  "environment": "Production",
  "solutions": [
    {
      "name": "customer-portal",
      "version": "1.3.0",
      "deployedAt": "2024-01-20T14:30:00Z",
      "deployedBy": "admin",
      "stateType": "deployed"
    }
  ]
}

And a solution’s version across environments:

{
  "solution": "customer-portal",
  "environments": {
    "Development": "1.4.0",
    "Staging": "1.3.0",
    "Production": "1.3.0"
  }
}

Best Practices

1. Monitor State Regularly

• Check which version is deployed per environment
• Review deployment history
• Identify stale environments

2. Keep Environments Synchronized

Promote versions through the pipeline:

Development (1.4.0) → Staging (1.3.0) → Production (1.3.0)
           ↓                  ↓
        Promote           Promote
           ↓                  ↓
Development (1.4.0) → Staging (1.4.0) → Production (1.4.0)

3. Document Significant Changes

Track why versions were deployed:

Date	Environment	Version	Reason
Jan 20	Production	1.3.0	Feature release
Jan 15	Production	1.2.1	Security patch
Jan 10	Production	1.2.0	Bug fix release

4. Use State for Troubleshooting

When issues occur:

1. Check current state
2. Compare to previous states
3. Identify recent changes
4. Roll back if needed

Troubleshooting

State Shows Wrong Version

Cause: Deployment may have failed partially

Solution:

1. Check deployment status
2. Verify target-level results
3. Redeploy if needed

State Not Updating

Cause: Deployment still in progress or failed

Solution:

1. Check deployment progress
2. Review logs for errors
3. State is read-only and derived from deployment records; if state appears stale, check whether the deployment itself is still in progress or has failed (see deployment logs)

Missing Solution in State

Cause: Solution never deployed to environment

Solution:

1. Create deployment to environment
2. Or use promotion from earlier environment

Next Steps

• Creating Environments - Set up environments
• Target Assignment - Assign targets
• Promotions - Promote between environments
• Overview - Return to environments overview