# Locating Outputs

When your workflow completes, Workbench helps you locate your output files without directly managing the files themselves. The actual file locations are determined by your workflow engine configuration.

## Understanding Output Locations

Output files remain in the storage location specified by your workflow engine. While Workbench doesn't move or copy these files, it provides a detailed list of output locations through the workflow run's monitoring page.

## Viewing Your Outputs

To find your workflow outputs:

1. Navigate to your run's details page through the Monitor page
2. Select the "Outputs" tab
3. View the JSON-formatted output list, where:
   * Keys are output variable names from your WDL workflow
   * Values are full file paths to your outputs

For example:

{% code overflow="wrap" %}

```json
"test.hello.response": "gs://workspaces-wes-staging/test/f00d7a09-49b3-4a0f-9d53-fdc5683cb792/call-hello/stdout"
```

{% endcode %}

## Cloud Storage Locations

File paths indicate your cloud storage platform:

* Google Cloud paths begin with `gs://`
* Amazon Web Services paths begin with `s3://`
* Microsoft Azure paths have no special prefix

### Working with Output Files

To work with your output files:

* Download the complete JSON output list using the "Download" button
* Copy the JSON contents using the "Copy" button for programmatic access
* Use your cloud provider's recommended tools to move or copy files

{% hint style="info" %}
Contact your IT administrator for guidance on the best methods to transfer or manage output files in your environment.
{% endhint %}


---

# 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.omics.ai/products/workbench/getting-started/locating-workflow-outputs.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.