# Validating

Scaffold validate is a `stoobly-agent` CLI command used to validate application workflows.

## Background

{% content-ref url="/pages/mrxE2H3fxfCSRj8hF0QQ" %}
[Validation](/core-concepts/scaffold/validation.md)
{% endcontent-ref %}

## Command

```bash
stoobly-agent scaffold workflow validate <WORKFLOW-NAME>
```

### Arguments

<details>

<summary>&#x3C;WORKFLOW-NAME></summary>

Name of the Stoobly workflow you want to validate. Workflows available by default:

* mock
* record
* test

</details>

### Options

<details>

<summary>--app-dir-path</summary>

path to the directory where your scaffolded application is.

</details>

## Example

In this example, we have created our scaffolded application in `./app` and are looking to validate the `record` workflow. The `record` workflow comprises of two services called `example-service` and `example-custom-container-service`. Our goal with the following command is to ensure that application is ready for recording requests.

```bash
$ stoobly-agent scaffold workflow validate --app-dir-path ./app record
```

After running a series of checks and collecting the results, here's an example output:

```
Validating workflow: record

Validating core services: ['build', 'entrypoint', 'stoobly-ui', 'gateway']
Validating core service: gateway
Validating core service: stoobly-ui
Validating setup containers: record-build.init-1
Validating core service: entrypoint
✔ Done validating core services for workflow: record, success!

Validating service: example-service
Validating hostname: example.com
Validating hostname exists in hosts file for hostname: example.com
Correct hosts mapping found for example.com
Validating connection to hostname: example.com, port: 443
Validating setup containers: record-example-service.init-1
Skipping validating public folder in workflow: record, container: record-example-service.init-1
Validating proxy container: record-example-service.proxy-1
Skipping validating public folder in workflow: record, container: record-example-service.proxy-1
✔ Done validating service: example-service, success!

Validating service: example-custom-container-service
Validating hostname: example-custom-container-service.com
Validating hostname exists in hosts file for hostname: example-custom-container-service.com
Correct hosts mapping found for example-custom-container-service.com
Validating connection to hostname: example-custom-container-service.com, port: 80
Validating setup containers: record-example-custom-container-service.init-1
Skipping validating public folder in workflow: record, container: record-example-custom-container-service.init-1
Validating proxy container: record-example-custom-container-service.proxy-1
Skipping validating public folder in workflow: record, container: record-example-custom-container-service.proxy-1
Validating local user defined service: example-custom-container-service
✔ Done validating service: example-custom-container-service, success!

✔ Done validating Stoobly scaffold and services, success!
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stoobly.com/guides/how-to-integrate-e2e-testing/how-to-run-a-workflow/troubleshooting/validating.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.