# 🌀 Execution Status and Lifecycle

Each execution in CCP is monitored through a status file called `metadata_jobStatus.json`.

This file records timestamps and current state of the execution, providing essential information for tracking progress and diagnosing issues.

---

## 🧭 Typical Lifecycle States

An execution may go through the following states:

- **accepted**: the job has been received and is in the queue
- **running**: execution has started in the container
- **successful**: method completed without error
- **failed**: method terminated with an error
- **cancelled**: execution was aborted manually
- **expired**: job took too long or lost resources

These states are automatically updated and can be queried via the CCP interface or REST APIs.

---

## 📄 File: `metadata_jobStatus.json`

This file is part of the execution’s metadata folder.

### Key fields:

- `jobID`: unique identifier of the execution
- `status`: current or final state (e.g., `successful`, `failed`)
- `created`: timestamp of job submission
- `started`: execution start time
- `updated`: last status update
- `message`: diagnostic message or termination reason
- `links`: references to other metadata (e.g., PROV-O)

---

### 🧪 Example

```json
{
  "jobID": "7de21671-...",
  "status": "successful",
  "message": "Runtime removed",
  "created": "2025-03-25T09:40:54Z",
  "started": "2025-03-25T09:40:54Z",
  "updated": "2025-03-25T09:51:33Z",
  "links": [
    {
      "href": "http://registry:8080/executions/7de21671-...",
      "rel": "prov"
    }
  ]
}
```

---

## 🔗 Related Pages

- ⏯️ [Understanding executions](./01_executions)

- 📂 [Execution outputs and logs](./02_outputs_and_logs)

- 📑 [Generated metadata files](./04_metadata_files)