Platform administration
Platform troubleshooting
Diagnose missing resources, access failures, secret selection and cross-product setup issues.
Start with identity and scope. An empty list can be the correct result for the selected workspace or permissions.
| Symptom | Check first |
|---|---|
| Page or action is missing | Organization/workspace selection, roles, groups and direct grants. |
| API returns unauthorized | Service base URL, accepted authentication scheme and credential validity. |
| Resource returns forbidden or not found | Tenant IDs and collection or instance permissions. |
| Secret selector is empty | Vault scope, secret existence and namespace permissions. |
| Connection validation fails | Connector availability, network reachability, required fields and secret references. |
| Cluster cannot start | Available node type, capacity, lifecycle state and permissions. |
| QuickFlow fails | Both connections, cluster readiness, selected streams, cursor settings and run details. |
| Schedule does not launch | Active schedule, parent flow and usable compute/connections. |
| Graph search is empty | Scope, context, filters, visibility and search-document state. |
| Lineage is incomplete | Direction, depth, relationship filters and whether entity or field edges were ingested. |
Follow the affected resource
- Use secret vault troubleshooting when a credential reference is missing.
- Use VegaFlow troubleshooting for connection, compute and run failures.
- Use VegaGraph troubleshooting for identity, search, context and lineage failures.
- Check VegaDB connection settings and federated-query troubleshooting for SQL access and external catalogs.
Share a support case
Include the time, service, operation, request ID, organization/workspace IDs, affected resource IDs and a redacted error. Describe the expected result and the checks already performed.
Keep access tokens, API keys, passwords, recovery codes and secret values out of the report. Contact Vegalake support when the product checks do not isolate the problem.