Troubleshooting
Use this page when a previously working enterprise-connected environment stops behaving as expected or when initial setup does not complete cleanly.
Audience: Enterprise end users, operators, and administrators
Common Problem Areas
Sign-in problems
If users cannot sign in or reach the correct organization context:
- confirm they are using the right invitation or sign-in route
- confirm their role or membership still exists
- verify they are targeting the intended environment
Connection problems
If a runtime or workspace does not appear connected:
- confirm the approved enterprise connection details are in use
- verify the environment is connecting to the correct enterprise destination
- re-check that the workspace belongs to the intended organization context
Access mismatch
If the wrong users can see an environment, or the right users cannot:
- review team membership
- review role assignments
- confirm the environment was connected under the correct organizational ownership
Operational visibility gaps
If monitoring, workflow, or reporting surfaces look incomplete:
- confirm the environment is still connected
- confirm the relevant workflow actually ran in the expected organization context
- check for broader health or connectivity issues before assuming data loss
A Safe Troubleshooting Sequence
- Verify the user and organization context.
- Verify the environment is the one you intended to inspect.
- Verify connection status.
- Review recent changes to access, configuration, or rollout state.
- Escalate with concrete symptoms, timestamps, and environment details if the problem persists.
When To Escalate
Escalate when:
- multiple users lose access unexpectedly
- a production environment disconnects repeatedly
- shared monitoring or reporting becomes unavailable
- you cannot confirm the correct organization or workspace ownership
Related Pages
For enterprise support or triage, contact support@garudexlabs.com.