# ⏯️ Understanding Executions

An **Execution** represents the instantiation of a method with a specific set of inputs and parameters.

Each time a user runs a method, CCP creates a new execution record, which includes all the required data to trace what was done, how, where, and with what inputs.

---

## 📁 Execution Structure

Each execution contains the following key components:

```sh
execution/ 
├── metadata/ 
│ ├── request.json 
│ ├── method.json 
│ ├── infrastructure.json 
│ └── instance.json 
├── auth/ 
│ └── jwt.json 
├── outputs/ 
│ ├── output.x
│ ├── output.y
│ └── output.z

```

This structure ensures that all necessary data for understanding and reproducing an execution is preserved.

---

## 🧪 Workbench

Executions are stored temporarily in a personal **Workbench**, which acts as a transient area for:

- Draft executions
- Testing methods
- Debugging and reconfiguration

Executions remain in the Workbench until manually deleted or explicitly exported.

---

## 📤 Exporting Executions

Users can export any execution to their **D4Science Workspace** by selecting the archive option.  
This generates a ZIP file containing all outputs and metadata. The exported path is usually:

`<workspace_root>/CCP/executions/<execution-name>.zip`


Executions can also be imported again from the Workspace or via a shared URL.

---

## 🔄 Re-execution

Any execution present in the Workbench can be re-run with the same parameters, or adapted with new inputs before submission.

To resubmit an execution, just press the **Re-Submit** button in the exeution monitor

To adapt adapted with new inputs before submission, click on the "Direct Link" button to open the execution form, prefilled with the previous inputs.

---

## 🔗 Related Pages

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

- 🌀 [Execution status and lifecycle](./03_execution_status)

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

- 📜 [Execution provenance (PROV-O)](./05_metadata_provo)