The permissions modal displays.
2. Depending on your permissions, you can use the dropdowns to update permissions for any person or group in your instance.
### Edit a Workflow
### Manage Workflow Versions
You cannot edit a workflow after it's been *deployed*. Instead, you must create a new version of the workflow—like a **Save As** —and edit the new *version*. A single workflow can have multiple versions, each with its own version number in *\<\
In the **Versions** tab, the listed **contributor** is the version creator, which can differ from the workflow creator.
Selecting a version from the list opens the canvas and displays the version's graphical model in the least restrictive mode based on your permissions and the model's status:
* If the version is *deployed*, the model opens in view only mode. You cannot edit a deployed version. To edit, you must create a new version.
* If the version is *pre-deployed* and you have only Read [permission](#manage_permissions) for the workflow, the model opens in view only mode.
* If the version is *pre-deployed* and you have Write or Admin [permission](#manage_permissions) for the workflow, the version opens in edit mode. Learn how to [design a workflow](https://domo-support.domo.com/s/article/000005331?language=en_US#design_your_workflow).
# Version Actions
In the **Versions** tab, the 
Action | Required Permission | Description |
|---|---|---|
View Only | View, Edit, or Admin | Opens the version in view-only mode. |
Edit Workflow | Edit or Admin | \*\*This is only available if the version has not been deployed. Opens the version in edit mode. |
Edit Version Details | Edit or Admin | Opens a modal where you can edit the version description. |
Create New Version | Edit or Admin | Opens the Create New Version modal. Learn how to create a new version. |
Deploy | Deploy or Admin | Attempts to deploy the version. A version can't run until it's been deployed. Deploying a version activates it by default. If there are validation issues, you are required to resolve errors before deployment. |
Activate / Deactivate | Edit or Admin | Deactivates/activates a deployed version. A version can't run until it's active. Deploying a version activates it by default. You can deactivate the version to keep it from running, but you can't "undeploy" it after it's been deployed. A deactivated version can't be started. |
Start | Execute or Admin | Initiates a workflow execution, including launching a form start. |
Go to Executions List | View Execution List, Edit Execution Details, or Admin | Opens the Executions tab. |
Delete | Delete or Admin | Deletes the version. |
* **Blank Canvas —** Selecting this option creates a new version of the workflow without using a previous version as a starting point.
* **Existing Version —** Selecting this option displays a list of all previous versions of the workflow. You can make changes to any version's configuration and save it as a new version. Select any of the available versions to number your new version, add an optional description, and open it in the canvas. If you change the default version number, it must be in the *\<\
2. Select **Add Trigger** > **\< *trigger type>***.
Each trigger type has its own setup requirements. After configuration, the trigger will be listed here in the **Triggers** tab.
* **App Studio —** Go to the App Studio app where you want the trigger to originate and add the Workflow widget. Locate and choose the correct version of the workflow.
In the image below, there are three available versions of the Resume Screening workflow. You want to trigger version 2.0.0 from inside your app, so you choose that version.
* **Pro-Code app —** Choose an existing app from the Asset Library configured with a workflow and map it to a card, or use the Pro-code Editor to build a new app. Program the app design to use a workflow, which can be selected and mapped via the card configuration panel.
* **Alerts —** Go to the DataSet's Details page and navigate to the **Alerts** tab. While creating a new Alert or editing an existing one, set the Action as the workflow version you want to execute when the Alert is triggered. Learn how to [create an Alert](/s/article/360042925994).
* **Workflow —** Learn how to [create a workflow trigger](#workflow_trigger) to trigger one workflow with another.
* **Timer —** Choose the workflow version and configure a timer with an update interval and start time. The available update intervals are as follows:
* **Every Minute —** Displays a **Minute Duration** dropdown with options for Every Minute, Every 5 Minutes, and Every 15 Minutes.
After selecting an option, you can optionally check the box labeled **Start Between** and choose the start and end times between which the workflow runs on the interval if you only want the workflow to run during certain hours of the day.
* **Every Hour** **—** Deploys the workflow every hour.
Optionally, you can check the box labeled **Start Between** and choose the start and end times between which the workflow runs every hour. If the **Start Between** box is unchecked, the workflow runs once per hour, 24 times per day.
* **Every Day** **—** Deploys the workflow once every day. In the Start field, select the hour you want the workflow to start. The **End** field automatically populates based on the chosen start field.
* **Every Weekday** **—** Deploys the workflow one time every weekday (Monday – Friday). The workflow doesn't start on weekend days (Saturday & Sunday). You must select the hour for the workflow to start in the **Start** field. The **End** field automatically populates based on the chosen start field.
* **Every Week** **—** Deploys the workflow once per week. In the **On this day** field, select the day you want the workflow to start and the hour of the day that it should start.
* **Every Month** **—** Deploys the workflow once per month on a specified day. Choose an option from the **On this day** dropdown. The options are the 1st of the month, the 15th of the month, and the Last day of the month. After choosing an option, choose the hour of the day that the workflow should start.
* **API trigger —** Choose the workflow version. Syntax is generated in JavaScript and Python. It contains a trigger ID. You can copy and paste the syntax into the API call. Any calls made with this trigger ID will be exclusively used for tracking purposes so you can identify which trigger initiated your workflow.
1. View your configured trigger in the **Triggers** tab. You can also view and configure triggers for deployed versions from the **Triggers** [tab](https://domo-support.domo.com/s/article/000005331?language=en_US#left_panel) in the canvas.
2. Select the **Start Workflow** package.
3. Locate the target workflow in the function list and map the necessary parameters.
4. Save your changes.
3. Deploy the triggering workflow.
The workflow trigger displays in the **Triggers** tab for that workflow.
# Delete a Trigger
You can delete triggers from Alerts, App Studio, Pro-code apps, and Workflows from the feature where it was configured.
Delete a trigger from a timer or API call by using the 
### View Workflow Executions
Owners and those with Admin [permission](#manage_permissions) can view a workflow's executions. Others can see or edit the workflow's executions if they have View Execution List and/or Edit Execution Details permission to the workflow.
From the Workflows home, select **More** (horizontal three-dot icon) > 
* Choosing to filter by a longer time period may require more time to return results.
Check the box for each workflow you want to cancel, or check the top box to "select all." Then select **Cancel executions**.
**Note:** The more workflows you cancel, the longer the request takes to process.
# Review Execution Details
If you have View Execution List [permission](#manage_permissions) to the workflow, you can select an execution from the **Executions** tab to view details about it, like how long a certain shape took to execute or the shape where the execution failed.
The execution details display in the Workflows canvas, which includes the execution's current status, [playback controls](#playback_controls), and a resizable data panel at the bottom of the screen.
Executed workflows can have one of the following four statuses:
* Complete
* In Progress
* Canceled
* Failed
On the canvas, completed shapes display outlined in green, and any shape currently in progress is outlined in blue. If the execution was stopped before one or more shapes completed, the execution status is Canceled; if any shapes failed before completing, they are outlined in red and the execution status is Failed.
The following table describes the playback controls:
Icon | Control | Description |
|---|---|---|
| Toggle | Controls whether the screen begins to auto-play the execution or displays the furthest point reached in the flow. |
| Replay | Replays the execution from the first start shape. |
| Play | Plays or resumes the execution from the last stopped point. |
| Stop | Stops/pauses the execution playback. |
| Fast Forward | Increases the speed of playback. There are four speeds, and repeatedly selecting the button cycles through them. |
User Tasks and Code Functions display inputs and outputs, while other shapes display the actual values of the variables when the shape was activated.
For shapes that were activated multiple times, you can page through the iterations in the data panel to see the data for each iteration.
### Recover/Retry an Execution
If you have Edit Execution Details [permission](#manage_permissions) to a workflow, you can recover failed executions of the workflow. Recovery means that you can **a)** try to update the data at the errored shape and then **b)** retry the execution.
In Recovery mode, a banner at the top of the screen displays the recovery options, which are described below.
# Recovery Options
The available recovery options include:
* **Exit Recovery —** Takes you back to view only mode.
* **Retry —** Attempts to run an execution again from where the workflow failed or is currently in progress.
* **Cancel Instance —** Stops a workflow execution and updates the status to Canceled.
# Edit Execution Data
While in Recovery mode, you can change input data at the current or last active point in the execution before attempting to retry it. To do this, locate the input you want to change in the data panel and select 
After making your changes, make sure to select 
Change as many data inputs on the shape as needed before selecting the **Retry** option in the banner.
### Cancel Workflow Executions
If you have a workflow execution in an In Progress status and you know it will never reach a Completed status, it is best practice to cancel it so that it displays properly in the logs and doesn't get updated by mistake.
If a User Task updates to Canceled, the task automatically voids in [Task Center](/s/article/000005172).
