> ## Documentation Index
> Fetch the complete documentation index at: https://control.datarelay.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Follow the Stream Wizard with Screenshots

> Use numbered annotations on genuine Control test captures to select a Connector, test records, map fields, deploy and verify Logs.

# Follow the Stream Wizard with Screenshots

> [!WARNING]
>
> These are **genuine historical Control UI test screenshots**, cropped and numbered for explanation. They show an older **six-step Wizard**, whereas the current product flow is **Connect → Sample & Record Selection → Destinations → Route Processing → Deploy**. Follow the current UI's sequence, not the old step numbering visible inside these captures. Screenshots are not proof of delivered events.

**Before you start:** use [connector-specific guides](https://control.datarelay.run/use-cases/index.md) to prepare official API docs, least-privilege credentials, sanitized samples and a reachable Destination.

## 1. Select the saved Connector

Create the Connector first, then select it under **Connect**. Verify the real Vendor/Source values.

![select-connector — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/select-connector.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=595bbed2cfdba81a0a246ed84116cc33)

*Figure 1. **Selecting an existing Connector.** ① Select your saved Connector (Generic REST is a test example). ② Continue to Sample. The Connector tab is already active.*

## 2. Run a collection test

Use **Run Test** to fetch samples and inspect status/record count. A successful test does not auto-confirm the record path.

![run-test — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/run-test.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=b608f03405b24c6b130a215599571177)

*Figure 2. **Testing collection and record count.** ① Run Test → ② verify HTTP status and extracted record count → ③ open Record Selection. An HTTP success is not proof of Destination delivery.*

## 3. Confirm record path and checkpoint

Select the true event array in JSON Tree, then a reliable checkpoint field. Confirm suggestions; do not accept them blindly.

![record-selection — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/record-selection.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=196de1ecaf541296095434008afc05ad)

*Figure 3. **Choosing record path and checkpoint.** ① Review the suggested Record Path, ② inspect actual fields in JSON Tree, ③ select the Checkpoint Field. This capture shows the not-yet-confirmed state.*

## 4. Verify mapped JSON output

Compare Sample, Mapping and Preview in **Route Processing / Transform**. Configure Route differences after selecting Destinations.

![field-mapping — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/field-mapping.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=15ae79d8a5249262f236f997f253d286)

*Figure 4. **Mapping an event to output fields.** ① Inspect the source sample, ② configure Field Mapping, ③ compare Final Event Preview. A preview does not prove real delivery.*

## 5. Add a custom field

If required, use **Add field → Static Value**. Close the menu and verify the field appears in Preview.

![add-static-field — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/add-static-field.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=d5f7d0d19193036e2aa71d7d4c4a6a62)

*Figure 5. **Adding a custom output field.** ① Select Add field, ② choose Static Value, then ③ close the menu and verify the new field in Final Event Preview.*

## 6. Resolve deploy blockers

If **NEEDS ATTENTION** appears, use **Edit** for Data/Records, correct the problem and re-check readiness.

![deploy-readiness — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/deploy-readiness.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=2eb8b8ba351102cfa1b039c59c529986)

*Figure 6. **Resolving a blocked deployment.** ① Read NEEDS ATTENTION, ② use Edit on Data/Records to fix required inputs, ③ stop while the deployment button is disabled.*

## 7. Check Stream runtime after creation

After Stream creation, use **Start Stream** and **View logs** to confirm execution. This capture explicitly says **Runtime API unavailable**.

![stream-actions — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/stream-actions.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=f5462ebde85e05d0c95ab32096a1a24e)

*Figure 7. **Start and verify a newly created Stream.** ① Review Stream creation, ② use Start Stream only when runtime is available, ③ open View logs to verify execution. This historical capture says Runtime API unavailable.*

## 8. Investigate operational health

Inspect dashboard window, Health and Alerts; validate actual delivery through Route Logs and receiver data.

![dashboard-triage — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/dashboard-triage.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=f9c658cdeaa4638d8010ca10721745f1)

*Figure 8. **Beginning an investigation on Dashboard.** ① Set the time window, ② inspect Health/Critical, ③ use Recent Alerts for context. Verify the root cause in Streams, Routes and Logs.*

## Failure example: HTTP 503 on Source API Test

This is a **Source API Test failure**, not a Destination error. Check vendor API status and configuration before retrying.

![source-api-error — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/source-api-error.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=c66a05ef28da079c34e48a36ed217113)

*Figure 9. **HTTP 503 during Source API Test.** ① Read the HTTP 503 error, ② repair the source and Retry, ③ do not proceed while blocked. This is a Source API Test failure, not a Destination failure.*

## Optional: resume a saved draft

Use **Resume draft** to continue retained settings. Only choose **Start fresh** when you intend a new configuration.

![saved-draft — numbered Control historical UI capture](https://mintcdn.com/datarelay-control/Tl9_UibGAprPlCr8/images/screenshots/annotated/saved-draft.webp?fit=max\&auto=format\&n=Tl9_UibGAprPlCr8\&q=85\&s=92631991e209b6fc9696bf4e1adfe263)

*Figure 10. **Resuming a saved Wizard draft.** ① Select Resume draft to continue existing settings or ② Start fresh for a new configuration. Preserve your draft before starting over.*

***

**Completion check:** a Stream run ID, a successful Route delivery log, and **actual Destination receipt** must match. See [Webhook walkthrough](https://control.datarelay.run/use-cases/webhook-first-flow.md) and [Logs evidence](https://control.datarelay.run/use-cases/logs-audit.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.