From 66c9f210b6248e0ea590defcc20f3507e014e0ad Mon Sep 17 00:00:00 2001 From: Vincent <0426vincent@gmail.com> Date: Fri, 3 Jan 2025 22:58:26 -0800 Subject: [PATCH] docs: update URL in local workflow execution guide to reflect project name Signed-off-by: Vincent <0426vincent@gmail.com> --- .../running_a_workflow_locally.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user_guide/getting_started_with_workflow_development/running_a_workflow_locally.md b/docs/user_guide/getting_started_with_workflow_development/running_a_workflow_locally.md index ce549889f0..921657b114 100644 --- a/docs/user_guide/getting_started_with_workflow_development/running_a_workflow_locally.md +++ b/docs/user_guide/getting_started_with_workflow_development/running_a_workflow_locally.md @@ -144,7 +144,7 @@ pyflyte run --remote -p my-project -d development example.py wf --name Ada You should see a URL to the workflow execution on your demo Flyte cluster, where `` is a unique identifier for the workflow execution: ```{prompt} bash $ -Go to http://localhost:30080/console/projects/flytesnacks/domains/development/executions/ to see execution in the console. +Go to http://localhost:30080/console/projects/my-project/domains/development/executions/ to see execution in the console. ``` ### Inspecting a workflow run in the FlyteConsole web interface