# Error: No context named 'deploy-prod' found. Please create the context or check the context name.

- **ID:** `cicd/circleci-no-context`
- **Domain:** cicd
- **Category:** config_error
- **Error Code:** `CIRCLECI_CONTEXT_MISSING`
- **Verification:** ai_generated
- **Fix Rate:** 90%

## Root Cause

CircleCI pipeline references a context name that does not exist in the organization's context list, often due to typo, context deletion, or insufficient permissions to access the context.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| CircleCI Server 4.0 | active | — | — |
| CircleCI CLI 0.1.30000 | active | — | — |

## Workarounds

1. **List all available contexts via CircleCI CLI: `circleci context list --org-id <org-id>`. If 'deploy-prod' is missing, create it: `circleci context create <org-name> deploy-prod` and add required environment variables via UI or CLI** (95% success)
   ```
   List all available contexts via CircleCI CLI: `circleci context list --org-id <org-id>`. If 'deploy-prod' is missing, create it: `circleci context create <org-name> deploy-prod` and add required environment variables via UI or CLI
   ```
2. **Verify the context name in the CircleCI config file (.circleci/config.yml) matches exactly (case-sensitive) the context created in the CircleCI web UI under Organization Settings > Contexts** (90% success)
   ```
   Verify the context name in the CircleCI config file (.circleci/config.yml) matches exactly (case-sensitive) the context created in the CircleCI web UI under Organization Settings > Contexts
   ```

## Dead Ends

- **** — The pipeline will find the context but fail later because required secrets (e.g., AWS keys) are missing from the empty context (80% fail)
- **** — The 'default' context may not exist or may not contain the required environment variables, causing subsequent steps to fail with missing credentials (60% fail)