Skip to content

Compose Troubleshooting

For the shared debugging workflow, start with Debugging and Troubleshooting. It explains Debug Events, instance debug, and the relationship between workflow state and live resource state.

Compose Troubleshooting Checklist

Use omnistrate-ctl instance debug <instance-id> to open the Compose resource and work through the following:

  1. Review application logs for container startup, health-check, or dependency errors.
  2. Confirm deployment API parameters resolved to the expected runtime values.
  3. Confirm deployment output parameters contain the values other resources or customers expect.
  4. Check workflow events to identify whether the failure happened during bootstrap, storage, network, compute, deployment, or monitoring.
  5. Use the Metrics tab or omnistrate-ctl instance dashboard <instance-id> to verify dashboard access when metrics are enabled.

The shared Compose Troubleshooting Checklist contains the same operational checks alongside the Helm, Operator, and Terraform checklists.

Publishing Changes

If you change the Compose specification, parameter mappings, source artifacts, or rendered configuration, publish a new Plan version and trigger a fresh workflow. Use Workflows to distinguish a retry of the same released artifacts from a new version.