You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/showcase/local-direct-execution.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,4 +84,4 @@ The run has no data dependency and therefore reports zero transferred bytes. Use
84
84
| The activity writes no artifact | The run only records changes made below its activity workspace. Make the command write relative to its working directory, as this example does. |
85
85
| The wrong machine executes the command | Direct execution always occurs on the daemon host. Run a daemon in the target environment, or use a remote runtime such as Kubernetes or SLURM instead. |
86
86
87
-
Read [Execution modes and runtimes](../explanations/runtimes) for the execution boundary and [Workflow runs](../guides/workflows/execution) for monitoring and cancellation.
87
+
Read [Execution modes and runtimes](../runtimes) for the execution boundary and [Workflow runs](../guides/workflows/executions) for monitoring and cancellation.
0 commit comments