diff --git a/docs/content/concepts/automation/schedules/testing.mdx b/docs/content/concepts/automation/schedules/testing.mdx index f742ba3a06a33..0b11946fa49a4 100644 --- a/docs/content/concepts/automation/schedules/testing.mdx +++ b/docs/content/concepts/automation/schedules/testing.mdx @@ -17,7 +17,7 @@ Using the UI, you can manually trigger test evaluations of a schedule and view t 2. Click the schedule you want to test. -3. Click the **Test Schedule** button, located near the top right corner of the page. +3. Click the **Preview tick result** button, located near the top right corner of the page. 4. You'll be prompted to select a mock schedule evaluation time. As schedules are defined on a cadence, the evaluation times in the dropdown are past and future times along that cadence. @@ -32,9 +32,38 @@ Using the UI, you can manually trigger test evaluations of a schedule and view t height={1388} /> -5. After selecting an evaluation time, click the **Evaluate** button. +5. After selecting an evaluation time, click the **Continue** button. -A window containing the evaluation result will display after the test completes. If the evaluation was successful, click **Open in Launchpad** to launch a run with the same config as the test evaluation. +6. A window containing the evaluation result will display after the test completes. + + + + Results page after evaluating the schedule in the Dagster UI + +If the preview was successful, then for each produced run request, you can view the run config and tags produced by that run request by clicking the **{}** button in the Actions column. + + + +7. Click the **Launch all & commit tick result** on the bottom right to launch all the run requests. It will launch the runs and link to the /runs page filtered to the IDs of the runs that launched. + + + + Runs page after launching all runs --- diff --git a/docs/content/concepts/partitions-schedules-sensors/sensors.mdx b/docs/content/concepts/partitions-schedules-sensors/sensors.mdx index c3cd252cd84e1..b0a60be5ee3c4 100644 --- a/docs/content/concepts/partitions-schedules-sensors/sensors.mdx +++ b/docs/content/concepts/partitions-schedules-sensors/sensors.mdx @@ -319,7 +319,7 @@ In the UI, you can manually trigger a test evaluation of a sensor and view the r 2. Click the sensor you want to test. -3. Click the **Test Sensor** button, located near the top right corner of the page. +3. Click the **Preview tick result** button, located near the top right corner of the page. -4. You'll be prompted to provide a cursor value. You can use the existing cursor for the sensor (which will be prepopulated) or enter a different value. If you're not using cursors, leave this field blank. +4. You'll be prompted to provide a cursor value (optional). You can use the existing cursor for the sensor (which will be prepopulated) or enter a different value. If you're not using cursors, leave this field blank. -5. Click **Evaluate** to fire the sensor. A window containing the result of the evaluation will display, whether it's run requests, a skip reason, or a Python error: +5. Click **Continue** to fire the sensor. A window containing the result of the evaluation will display, whether it's run requests, a skip reason, or a Python error: - If the run was successful, then for each produced run request, you can open the launchpad pre-scaffolded with the config produced by that run request. You'll also see a new computed cursor value from the evaluation, with the option to persist the value. +6. If the preview was successful, then for each produced run request, you can view the run config and tags produced by that run request by clicking the **{}** button in the Actions column. + + + + Actions page in the Dagster UI + +7. Click the **Launch all & commit tick result** on the bottom right to launch all the run requests. It will launch the runs and link to the /runs page filtered to the IDs of the runs that launched. + + + + Runs page after launching all runs diff --git a/docs/content/concepts/webserver/ui.mdx b/docs/content/concepts/webserver/ui.mdx index 09da6f3b1670d..286ffbc14ebc3 100644 --- a/docs/content/concepts/webserver/ui.mdx +++ b/docs/content/concepts/webserver/ui.mdx @@ -297,7 +297,7 @@ height={1942} ### Schedule details -- **Description**: The **Schedule details** page contains details about a single schedule, including its next tick, tick history, and run history. Clicking the **Test schedule** button near the top right corner of the page allows you to test the schedule. +- **Description**: The **Schedule details** page contains details about a single schedule, including its next tick, tick history, and run history. Clicking the **Preview tick result** button near the top right corner of the page allows you to test the schedule. - **Accessed by**: Clicking a schedule in the [**Schedules** page](#all-schedules) @@ -340,7 +340,7 @@ height={1938} ### Sensor details -- **Description**: The **Sensor details** page contains details about a single sensor, including its next tick, tick history, and run history. Clicking the **Test sensor** button near the top right corner of the page allows you to test the sensor. +- **Description**: The **Sensor details** page contains details about a single sensor, including its next tick, tick history, and run history. Clicking the **Preview tick result** button near the top right corner of the page allows you to test the sensor. - **Accessed by**: Clicking a sensor in the [**Sensors** page](#all-sensors) diff --git a/docs/content/tutorial/scheduling-your-pipeline.mdx b/docs/content/tutorial/scheduling-your-pipeline.mdx index 5e48ae5f66b6f..b0d69fd839d90 100644 --- a/docs/content/tutorial/scheduling-your-pipeline.mdx +++ b/docs/content/tutorial/scheduling-your-pipeline.mdx @@ -56,7 +56,7 @@ width={1152} height={637} /> -To test the change, click the schedule's name to view its details. Click the **Test Schedule** button on the top right corner of the page to trigger the schedule immediately. +To test the change, click the schedule's name to view its details. Click the **Preview tick result** button on the top right corner of the page to trigger the schedule immediately.