Tenant Wizard Operations
Typical operator checks
- Verify the active company context before creating tenants as a privileged user.
- Confirm that the target CPI or Edge endpoints are reachable from the deployment environment.
- For
edge_hybrid, verify that the referenced CPI tenant already exists and is not itself an Edge tenant. - After create, check that worker jobs pick up the tenant and begin populating runtime data.
Common failure categories
- duplicate tenant name inside the same company
- missing active company assignment
- invalid or missing edge parent reference
- wrong auth mode or incomplete secret fields
- network-level connectivity problems during test calls
Operational follow-up after create
Creation alone does not guarantee visible monitoring data. Runtime jobs still need time to:
- sync packages
- fetch messages and payloads
- evaluate alerts
- populate archive and keystore views where configured