troubleshoot

To troubleshoot Facets infrastructure issues, describe the symptoms concisely. The system applies a structured thinking chain using Raptor CLI to query releases, resource status, and logs, forming hypotheses to provide root causes and verification steps.

Finding the root cause of broken Facets resources involves hypothesis-driven troubleshooting. The system automatically forms likely causes and queries resource status and logs to validate hypotheses, enabling faster restoration of services across environments.

Raptor CLI queries resource status, releases, and logs for incident management by gathering evidence to validate hypotheses. It applies a structured thinking chain to diagnose Facets infrastructure problems from symptoms and prescribe exact recovery actions.

Yes, you can use this approach to fix connectivity issues in your deployment. The system diagnoses and fixes Facets infrastructure problems from symptoms, applying guided fixes that prescribe exact commands and steps to implement recovery actions and verify results.

If Facets infrastructure troubleshooting is not working, ensure you describe the symptoms concisely and instruct the agent to diagnose, gather evidence, and prescribe a fix. The system relies on accurate symptoms to query logs and form correct root-cause hypotheses.