Common Issues

Solutions for the most frequently encountered issues. If your issue isn't listed here, contact engage@sentinelflux.in.

Generation pipeline issues

AppExplorer fails to access the application

Symptom: AppExplorer status shows "Connection refused" or "Timeout" in Agent Activities.

Causes and fixes:

1. The application URL is not publicly accessible. Verify the URL is reachable from an external network.
2. Your firewall or WAF is blocking VigilQA's IP ranges. Whitelist the IP ranges from Settings → Network → IP Allowlist.
3. The URL requires HTTPS but your staging certificate is self-signed. Use a valid certificate or contact support to configure certificate bypass for staging.

DocReview rejects all generated documents

Symptom: All scenarios fail DocReview and enter the Approvals queue as rejected.

Causes and fixes:

1. KB scenario steps are too vague. Add specific element names, page paths, and observable actions. See Knowledge Base best practices.
2. KB scenario expected fields don't specify observable outcomes. Replace "login works" with "redirected to /dashboard with user name visible".
3. AppExplorer didn't run before DocGen. Check that AppExplorer completed successfully for the affected domain.

ScriptReview fails with "selector not found"

Symptom: Scripts fail ScriptReview with errors like "selector 'button.checkout-btn' not found in locator map".

Causes and fixes:

1. AppExplorer's selector map is stale (the UI changed since the last crawl). Re-run AppExplorer from Generation → AppExplorer → Re-run.
2. The scenario references a page that AppExplorer didn't crawl. Check that the page path is listed in the domain's base_urls in the KB.

Test run issues

All Web UI tests fail with "Page not found"

Symptom: Every Web UI test fails immediately with a 404 or login redirect.

Causes and fixes:

1. The environment's base URL is incorrect or the application is down. Verify the URL in Project Settings → Environments.
2. Test credentials are invalid or the test user account has been deleted. Update credentials in Environments → [name] → Credentials.
3. The application requires a VPN or IP allowlist that the test runner can't reach. Check network access requirements.

Run stuck in "Running" status

Symptom: A run has been in "Running" state for longer than the configured timeout.

Causes and fixes:

1. The application is very slow to respond, causing individual tests to time out. Check application performance.
2. A specific test is hanging on a modal or JavaScript interaction. Check the live log stream in Agent Activities for the current test being executed.
3. Contact support if the run doesn't complete after 2× the configured timeout — it may need to be manually terminated.

CI/CD integration issues

API call returns 401 Unauthorized

Verify the API token is correct and has not expired. Generate a new token from Settings → API Tokens. Ensure the token is being passed in the Authorization: Bearer {token} header — not as a query parameter.

Run trigger returns 404

Check that the project and plan values in the request body exactly match the slugs shown in the dashboard. Project and plan names are case-sensitive.

Getting support

For issues not covered here:

• Email: engage@sentinelflux.in — include your project name, the run ID (if applicable), and a description of the issue
• Trial accounts: Priority email support with same-day response during business hours
• Enterprise accounts: Dedicated Slack channel and SLA-backed response times