Skip to content

Commit 386de7d

Browse files
authored
Update pause-purge.mdx
1 parent 888cde0 commit 386de7d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/content/docs/queues/configuration/pause-purge.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Pause and purge Queues
2+
title: Pause and Purge
33
pcx_content_type: concept
44
sidebar:
55
order: 2
@@ -8,7 +8,7 @@ import { WranglerConfig, Type, MetaInfo } from "~/components";
88

99
## Pause Delivery
1010

11-
You can pause delivery of messages from your Queue to any connected consumers. Pausing a Queue is useful when managing downtime (for example, if your consumer Worker is unhealthy) without losing any messages.
11+
You can pause delivery of messages from your queue to any connected consumers. Pausing a queue is useful when managing downtime (for example, if your consumer Worker is unhealthy) without losing any messages.
1212

1313
Queues continue to receive and store messages even while delivery is paused. Messages in a paused queue are still subject to expiry, if the messages become older than the queue message retention period.
1414

@@ -40,19 +40,19 @@ When a queue is paused, messages cannot be pulled by an [HTTP pull based consume
4040
## Purge queue
4141
Purging a queue permanently deletes any messages currently stored in the Queue. Purging is useful while developing a new application, especially to clear out any test data. It can also be useful in production to handle scenarios when a batch of bad messages have been sent to a Queue.
4242

43-
Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the Queue.
43+
Note that any in flight messages, which are currently being processed by consumers, might still be processed. Messages sent to a queue during a purge operation might not be purged. Any delayed messages will also be deleted from the queue.
4444

4545
:::caution
4646
Purging a queue is an irreversible operation. Make sure to use this operation carefully.
4747
:::
4848

4949
### Purge queue using Wrangler
50-
The following command will purge messages from your Queue. You will be prompted to enter the Queue name to confirm the operation.
50+
The following command will purge messages from your queue. You will be prompted to enter the queue name to confirm the operation.
5151
```sh
5252
$ npx run wrangler queues purge <QUEUE-NAME>
5353

54-
🚨This operation will permanently delete all the messages in Queue <name>. Type <name> to proceed.
54+
This operation will permanently delete all the messages in Queue <QUEUE-NAME>. Type <QUEUE-NAME> to proceed.
5555
```
5656

5757
### Does purging a Queue affect my bill?
58-
Purging a Queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a Queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.
58+
Purging a queue counts as a single billable operation, regardless of how many messages are deleted. For example, if you purge a queue which has 100 messages, all 100 messages will be permanently deleted, and you will be billed for 1 billable operation. Refer to the [pricing](/queues/platform/pricing) page for more information about how Queues is billed.

0 commit comments

Comments
 (0)