| Symptom | Check |
|---|---|
| No TREX item in the settings sidebar | Your organization doesn’t have TREX access. Contact Greptile. |
| TREX is on but never runs | When TREX runs is Sometimes and no rule matches, Automatic TREX runs excludes the event, or the author set TREX on my PRs to Off. |
| TREX was skipped for credits | The organization ran out of credits or hit its usage limit. See Billing. |
| The comment lists Blockers | Open the environment → Overview → Environment Health. Fix the setup script or setup instructions, rebuild, then run TREX Simulation. |
| ”No flows tested” | TREX couldn’t test anything. Check Blockers, and make sure the repository has a built environment. |
| A custom flow didn’t run | TREX didn’t find it relevant to the change. Make its description and goal specific. See Custom flows. |
| A custom flow is under Incomplete custom user flows | TREX couldn’t reach its starting point, or a check looks wrong. Click Edit flow and fix the starting point or checks. |
| TREX Simulation is disabled | The environment needs a successful build that matches the saved settings, you’ve used all 5 simulations for this configuration, or the repository isn’t on GitHub or GitLab. |
| A recording link returns “Artifact expired” | Recordings are kept for 30 days. |
TREX
Troubleshooting
Fix the common reasons TREX doesn’t run, can’t start your app, or skips a flow.