Troubleshooting

Solutions

• 1. Verify you're using the correct email address
• 2. Try the "Forgot Password" link to reset your password
• 3. Check if your account uses SSO (try "Sign in with Google/GitHub")
• 4. Ensure your account hasn't been suspended—check email for notices
• 5. Disable browser extensions that might block login

Solutions

• 1. Ensure your device clock is synchronized (codes are time-based)
• 2. Wait for the next code—don't reuse expired codes
• 3. Try your backup codes if you saved them
• 4. Contact support with proof of identity to reset 2FA

Solutions

• 1. Verify the API key is correct and complete
• 2. Check if the key has been revoked in Dashboard → Settings → API Keys
• 3. Ensure you're using the correct environment (test vs live keys)
• 4. Verify the key has the required scopes for your request
• 5. Check the Authorization header format: Bearer YOUR_API_KEY

Solutions

• 1. Check if you've reached your concurrent workflow limit
• 2. Verify your repository connection is still valid
• 3. Check if there are any organization-wide rate limits
• 4. Try canceling and restarting the workflow
• 5. Review the workflow configuration for errors

Solutions

• 1. Check the build logs for specific error messages
• 2. Verify your package.json or build configuration is correct
• 3. Ensure all environment variables are set in project settings
• 4. Check if dependencies are available and not blocked
• 5. Try building locally to reproduce the issue

# Check build logs
qodryx workflows logs <workflow-id> --stage build

Solutions

• 1. Provide more detailed and specific prompts
• 2. Include examples of expected output
• 3. Break complex requirements into smaller tasks
• 4. Reference existing code patterns in your repo
• 5. Use the iterate stage to refine generated code

Solutions

• 1. Large repositories may need increased timeout (Enterprise feature)
• 2. Exclude large binary files or vendor directories
• 3. Run partial scans on specific directories
• 4. Check if dependencies are downloading slowly

# Exclude directories in qodryx.yml
security:
  exclude:
    - "node_modules/**"
    - "vendor/**"
    - "*.min.js"

Solutions

• 1. Mark as false positive in the dashboard (will be suppressed)
• 2. Add inline ignore comments: // qodryx-ignore: RULE_ID
• 3. Configure rule exclusions in qodryx.yml
• 4. Report the false positive to help improve our scanners

Solutions

• 1. Verify your cloud credentials haven't expired
• 2. Re-authenticate the integration in Settings → Integrations
• 3. Check if required permissions were revoked on the provider side
• 4. Ensure the deployment target (project/environment) exists
• 5. Review cloud provider's IAM settings

Solutions

• 1. Check Vercel dashboard for build logs
• 2. Verify framework preset is correctly detected
• 3. Check for build errors in Next.js/framework logs
• 4. Ensure build output doesn't exceed Vercel limits
• 5. Cancel and retry the deployment

Solutions

• 1. Ensure CLI is installed: npm install -g @qodryx/cli
• 2. Check your PATH includes npm global bin directory
• 3. Try running with full path: npx @qodryx/cli
• 4. Restart your terminal after installation

# Check npm global path
npm config get prefix

# Add to PATH (Linux/Mac)
export PATH="$(npm config get prefix)/bin:$PATH"

Solutions

• 1. Run qodryx auth logout then qodryx auth login
• 2. Check if token file exists: ~/.qodryx/credentials
• 3. Verify token permissions with qodryx auth status
• 4. Try setting API key via environment variable:

export QODRYX_API_KEY=qx_live_your_key_here
qodryx projects list

Solutions

• 1. Reconnect GitHub in Settings → Integrations
• 2. Check if QODRYX app is still installed in GitHub settings
• 3. Verify repo permissions in GitHub App settings
• 4. Check webhook delivery status in GitHub repo settings
• 5. Ensure webhooks aren't being blocked by network policies

Solutions

• 1. Clear browser cache and cookies
• 2. Try a different browser
• 3. Disable browser extensions
• 4. Check your internet connection
• 5. Use pagination for large data sets