# Manual Runs

Manually running your workflow in MESA is an important final check of your automation setup. It allows you to see how your workflow will behave before going live with automatic runs.

You can (and should) manually run your workflow steps to confirm each one is working properly as you build. Manually running automations on a per-step basis doesn't impact the rest of the workflow and provides clarity on the order of operations as you go.

When you complete your workflow, you can manually run it from beginning to end as a final sanity check.

With access to live, example, or custom data, MESA allows you to manually run the workflow with real results directly in the builder.

## Manually Run When No Data is Available

Sometimes, you will not have any data available for the trigger you're using. If that's the case, you'll see the following message in the Manual run submenu of an open trigger:

*"**Records are required to run your workflow**"*

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FDshrZVx6X05PsDiMi0W4%2Fimage.png?alt=media&#x26;token=2d7ac5ea-3890-4d61-8b10-4865ddb51c26" alt=""><figcaption></figcaption></figure>

When you see this message, you will want to follow the instructions:

1. Check your connection
2. [Turn on](https://docs.getmesa.com/workflow-builder#enabling-your-workflow) your workflow
3. Perform the event in your connected app

For the example in the screenshot, you would need to create a new row in your connected Google Sheet while the workflow is enabled. After doing that, check back in on the workflow to view your available record.

## Manually Run With Your Data

Manual runs can be done with Live data, Saved data, or Advanced payloads.

Manually running your workflow with live data allows you to see the results of your automation with real examples from your store or third-party app.

The **Live records** list can be found by clicking the **Manual run** submenu in an open trigger.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FKEfE4jYBr2Z5ZSarrttR%2Fimage.png?alt=media&#x26;token=13460b43-6b7c-4339-a7a4-8df623a15f07" alt=""><figcaption></figcaption></figure>

From there, you can choose recent records from your store's data to edit, or conduct a manual run with as-is. Clicking **View record** next to any record allows you to view and edit the data included in your run.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2Fr5o9uyHLUUt151sugyXd%2Fimage.png?alt=media&#x26;token=c2b89e79-055b-4b75-b6e8-70cee308585f" alt=""><figcaption></figcaption></figure>

Once a manual run is conducted with any of your records, you will see the record and information of your run populate in the **Saved data** list of the Manual run submenu. This allows you to replay the same record multiple times, or slightly alter it with different information if you choose to edit the payload.

If you'd like to manually run the workflow with your own custom JSON or raw text payload, you will want to use the JSON field found in the **Advanced** tab of the Manual run submenu.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FRQgV66rSdW1wbWmkIzE0%2Fimage.png?alt=media&#x26;token=4a3b25fe-9a81-4017-9ae2-26528d87116d" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Conducting a Manual run will act as if the workflow is turned on, which means the impact of the workflow outcome will be live.&#x20;

For example, if you have a workflow that sends an email to the customer, you may want to set up a test order under your email address or change the email recipient field to your address instead. This will ensure that emails are not sent to your customers during manual runs.
{% endhint %}

## Manually Run Per-step

Manually running a single step can be done from the **Run step** button at the bottom of your opened action or trigger.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FepJExHYYuBNObmxpwITD%2Fimage.png?alt=media&#x26;token=0e962b1c-2cdf-4760-abdd-a5904d65d80b" alt=""><figcaption></figcaption></figure>

The manual run will process every step through (but not beyond) the step you ran. After this initial run, the prior steps will not be re-run if they have already been run once.&#x20;

The previously run values of those steps will be preserved until they are re-run.&#x20;

For example, if the previous step retrieved a product, running subsequent steps will have a cached version of the product that is used for future manual runs. If the product is updated in Shopify, then the product retrieve step will have to be run again for the rest of the steps to have the updated data.

{% hint style="info" %}
You will need to manually run the workflow from the trigger step before you can run a single step.
{% endhint %}

## Manually Run Your Entire Workflow

You can manually run your completed workflow via the **Run workflow** button at the bottom of the builder or in the trigger step with the Manual run submenu opened.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FUgRDZa4imI2reXRFGrpq%2Fimage.png?alt=media&#x26;token=1ef6ae81-77b7-4ecd-8101-1311f0abb7d9" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FZOFUIjXxKsBwWIJkerp1%2Fimage.png?alt=media&#x26;token=832a7c2d-f20f-49e2-8650-cbc97eeca283" alt=""><figcaption></figcaption></figure>

Once you begin the run, the builder will update to a view that shows the run's results on each step as they play out. By default, the manual run will stop if there is an error or if a Filter does not meet its conditions.

## View Your Results

Once your manual run has been completed, you can view the results in the steps themselves or within the workflow [Activity](https://docs.getmesa.com/workflow-activity).

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FWJNu1TzwgCFXhcfsrXPH%2Fimage.png?alt=media&#x26;token=a9a9b11b-08ff-4b67-8e7a-fe373186752c" alt=""><figcaption></figcaption></figure>

If you open a step after it has been manually run, you'll see the values associated with your run populate under the field representing the variable you're using.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FtQ7b143AUF09bgQR2AXB%2Fimage.png?alt=media&#x26;token=bc0e00d8-b1b9-4af6-be5d-ceb2368f0cfc" alt=""><figcaption></figcaption></figure>

You can also see a more detailed breakdown of your run by viewing it in the [Activity](https://docs.getmesa.com/workflow-activity) tab of your workflow.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FAe2mTSqlUbrEqbeIqxgr%2Fimage.png?alt=media&#x26;token=20540209-de20-41c7-af36-cf58e50ff1f6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FtFHRBiqJaqwBPk9UbUtn%2Fimage.png?alt=media&#x26;token=95458c41-3970-4a66-8056-6f1b03923137" alt=""><figcaption></figcaption></figure>

## Connectors With Unique Requirements for Manual Runs

The following triggers and actions have unique processes for manual runs.

#### [Webhook](https://docs.getmesa.com/tools/webhook)

You will want to conduct a manual run with your Webhook trigger by sending a notification from your third-party application.

To check the payload coming from your third-party application, click on the **Activity** tab of your workflow in the MESA dashboard. Then expand the recent run of your workflow, click the 3 vertical dots on the right side of the **Webhook** text, and then click **Request Details**.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2F8d4vAas37Suv9a5msjlW%2Fimage.png?alt=media&#x26;token=6463b1d9-1c04-4fb6-9cbe-9d8fe8dbbdc5" alt=""><figcaption></figcaption></figure>

#### [Web Request](https://docs.getmesa.com/tools/web-request)

You will need to send a POST request to the URL, or pass in a test payload in the Advanced tab of the Manual run menu. Once you conduct a manual run, the data will be available as variables for the next steps.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FNofhCi0ETPRjVxrBJAky%2Fimage.png?alt=media&#x26;token=2000376e-9e31-428f-8d0f-b275be091d4b" alt=""><figcaption></figcaption></figure>

#### [Forms](https://docs.getmesa.com/tools/forms)

To conduct a manual run for your Forms workflow, make sure that you enable your workflow. Locate the **Form URL** field and click on the external link icon to view your Form. Then, make a test submission.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FzTc7bHC6Xk9SVLZtEJu1%2Fimage.png?alt=media&#x26;token=c9742736-df4b-4271-a62f-67841595119b" alt=""><figcaption></figcaption></figure>

#### [Email](https://docs.getmesa.com/tools/email#trigger)

You can manually run the Email trigger by sending an email to the custom MESA email address associated with your step in the **Manual run** submenu while your workflow is enabled.

<figure><img src="https://3425906282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1H6u1HQc3Iew7ATmmiCi%2Fuploads%2FV3dpGsMvgQEd7LV3CgV0%2Fimage.png?alt=media&#x26;token=4472554b-94e9-4995-9baa-3d041eb95598" alt=""><figcaption></figcaption></figure>

## Additional Notes

* Steps that send notifications ([Email](https://docs.getmesa.com/tools/email), [Slack](https://docs.getmesa.com/apps/slack), [SMS](https://docs.getmesa.com/tools/sms), etc) will execute in manual runs, providing updates to these services with the information populated in the action. We strongly recommend replacing real data with your own info if you don't want others to see the results.