# Creating workflows for live optimizations

A workflow for a [live optimization study](https://docs.akamas.io/akamas-docs/3.1.2/akamas-reference/glossary/live-optimization-studies) automates all the actions required to interface the configuration management. Notice that metrics collection is an implicit action that does not need to be coded as part of the workflow.

<figure><img src="https://2641073690-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4ubiK4vpNilxkD7Fauar%2Fuploads%2FDPjAGE4IeizmXsqmYJW3%2FScreenshot%202023-01-17%20at%2015.29.53.png?alt=media&#x26;token=545edd6c-c398-4d33-ac15-cf68f55e712b" alt=""><figcaption><p>Automated workflow for a live optimization study</p></figcaption></figure>

More in detail, a typical workflow includes the following types of tasks:

* **Applying the configuration**, by preparing and then applying the parameter configuration that has been recommended and/or approved to the target environment - this may require interfacing configuration management tools or pushing configuration to a repository

Depending on the complexity of the system, the workflow might be composed by multiple actions of the same type, each operating on separate components of the target system.&#x20;

As expected, with respect to [workflows for offline optimization studies](https://docs.akamas.io/akamas-docs/3.1.2/using-akamas/preparing-optimization-studies/creating-automation-workflows/creating-workflows-for-live-optimizations), there are no actions to apply synthetic workloads as part of a load-testing scenario.&#x20;