# Error: Context 'deploy-aws' not found. Please create the context or check the context name.

- **ID:** `cicd/circleci-missing-context`
- **Domain:** cicd
- **Category:** config_error
- **Verification:** ai_generated
- **Fix Rate:** 95%

## Root Cause

A CircleCI pipeline references a context that does not exist in the organization, either because it was deleted, the name is misspelled, or the user lacks permissions to access it.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| CircleCI CLI 0.1.28000+ | active | — | — |
| CircleCI Server 4.0+ | active | — | — |
| CircleCI SaaS | active | — | — |

## Workarounds

1. **Create the missing context in the CircleCI web UI (Organization Settings > Contexts > Create Context) with the exact name 'deploy-aws', then restart the pipeline from the CircleCI dashboard.** (95% success)
   ```
   Create the missing context in the CircleCI web UI (Organization Settings > Contexts > Create Context) with the exact name 'deploy-aws', then restart the pipeline from the CircleCI dashboard.
   ```
2. **Correct the context name in .circleci/config.yml by verifying the existing context list via CLI: `circleci context list --org-id <org-id>` and updating the `context` field in the job.** (90% success)
   ```
   Correct the context name in .circleci/config.yml by verifying the existing context list via CLI: `circleci context list --org-id <org-id>` and updating the `context` field in the job.
   ```

## Dead Ends

- **Renaming the context in the CircleCI web UI without updating the .circleci/config.yml file** — The config file still references the old context name, causing the same error on the next pipeline run. (60% fail)
- **Creating a new context with the same name but in a different organization or team** — Contexts are scoped to organizations; a context in a different org is not accessible to the pipeline. (80% fail)