> For the complete documentation index, see [llms.txt](https://docs.stoobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoobly.com/core-concepts/scaffold/validation.md).

# Validation

When we encounter an error after a scaffolded workflow is run, we want to diagnose the cause. Scaffold validation does the following checks on your application:

{% tabs %}
{% tab title="Record" %}

* Core services are running
* Containers for each service are running
* Resource directories are mounted within the containers
* Requests can be recorded from each service
* Stoobly UI is running and accessible on localhost port 4200
  {% endtab %}

{% tab title="Mock" %}

* Core services are running
* Containers for each service are running
* Resources are mounted within the containers
* Requests can be mocked from each service
* Stoobly UI is running and accessible on localhost port 4200
  {% endtab %}

{% tab title="Test" %}

* Core services are running
* Containers for each service are running
* Resources are mounted within the containers
* Requests can be mocked from each service
  {% endtab %}
  {% endtabs %}

## Core Services

| Service    | Record | Mock | Test |
| ---------- | ------ | ---- | ---- |
| build      | ✅      | ✅    | ✅    |
| entrypoint | ✅      | ✅    | ✅    |
| gateway    | ✅      | ✅    | ❌    |
| stoobly-ui | ✅      | ✅    | ❌    |

## Service Containers

A service is comprised of one or more containers and belongs to one or more worfklows. When a workflow is run, the following containers will be started:

<table><thead><tr><th width="251">Container</th><th>Detached</th><th>With Hostname</th><th>Without Hostname</th></tr></thead><tbody><tr><td>&#x3C;WORKFLOW>-init</td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>&#x3C;WORKFLOW>-proxy</td><td>✅</td><td>✅</td><td>❌</td></tr></tbody></table>

## Resource Directory Mounts

<table><thead><tr><th width="169">Resource Directory</th><th width="269">Destination</th><th width="98">Detached</th><th>With/Without Hostname</th></tr></thead><tbody><tr><td>.stoobly</td><td>/home/stoobly/.stoobly</td><td>❌</td><td>✅</td></tr><tr><td>.stoobly/services</td><td>/home/stoobly/.stoobly/services</td><td>✅</td><td>✅</td></tr></tbody></table>

## Get Started

{% content-ref url="/pages/LmG9o2oN0VNqsBmYIhqz" %}
[Validating](/guides/how-to-integrate-e2e-testing/how-to-run-a-workflow/troubleshooting/validating.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.stoobly.com/core-concepts/scaffold/validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.