Skip to content

Commit 211b552

Browse files
committed
fix link formatting
1 parent a6c5e73 commit 211b552

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

src/content/docs/workflows/get-started/cli-quick-start.mdx

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ Specifically, the code above:
150150

151151
## 2. Deploy a Workflow
152152

153-
Workflows are deployed via [`wrangler](/workers/wrangler/install-and-update/), which is installed when you first ran `npm create cloudflare`, above. Workflows are Workers scripts, and deployed the same way:
153+
Workflows are deployed via [`wrangler`](/workers/wrangler/install-and-update/), which is installed when you first ran `npm create cloudflare`, above. Workflows are Workers scripts, and deployed the same way:
154154

155155
```sh
156156
npx wrangler@latest deploy
@@ -312,6 +312,20 @@ Steps:
312312
└────────────────────────┴────────────────────────┴───────────┴────────────┴───────────────────────────────────────────┘
313313
```
314314

315+
From the output above, we can inspect:
316+
317+
* The status (success, failure, running) of each step
318+
* Any state emitted by the step
319+
* Any `sleep` state, including when the Workflow will wake up
320+
* Retries associated with each step.
321+
* Errors, including exception messages
322+
323+
:::note
324+
325+
You do not have to wait for a Workflow instance to finish executing to inspect its current status. The `wrangler workflows instances describe` sub-command will show the status of an in-progress instance, including any persisted state, if it is sleeping, and any errors or retries. This can be especially useful when debugging a Workflow during development.
326+
327+
:::
328+
315329
## Next steps
316330

317331
* Learn more about [how events are passed to a Workflow](/workflows/build/events-and-parameters/)

0 commit comments

Comments
 (0)