Environment Strategy

Use this guide to keep staging and production traffic isolated.

Purpose

This guide helps you:

• Separate destinations per environment.
• Promote changes safely.
• Define rollback actions before production rollout.

Prerequisites and permissions

• Access to endpoint and relay-target management.
• Environment-specific destination URLs/inboxes.

Step-by-step workflow

1. Create environment-specific relay targets

Examples:

• billing-webhook-stg
• billing-webhook-prod

Include environment in target names/descriptions.

2. Create environment-specific endpoints

Examples:

• orders-intake-stg
• orders-intake-prod

Keep method/payload/security settings aligned unless differences are intentional.

3. Validate in staging first

1. Attach staging outputs only.
2. Send representative traffic.
3. Verify outcomes in Activity.
4. Confirm destination behavior.

4. Promote to production

1. Apply proven settings to production endpoint.
2. Verify prod secrets/certs.
3. Send controlled production check traffic.
4. Monitor Activity closely during rollout.

5. Document ownership and rollback

Per production endpoint, record:

• Owning team
• Destination owner
• Rollback action (disable endpoint, detach output, or rotate URL)

Expected result and verification checks

• Staging and production stay isolated.
• Promotion is repeatable and low-risk.
• Rollback can be executed quickly.

Common issues and fixes

• Traffic sent to wrong destination: enforce naming standards and review outputs before save.
• Production-only failures: recheck production-only auth/cert/headers.
• Confusing endpoint lists: use consistent prefixes/suffixes.

Related guides

• Endpoint Management
• Relay Targets
• Observability
• Incident Response