Temporarily stop (and/or rate limit) processing a task queue

[Slijkhuis]

We have some activities that call an external party. They sometimes suffer downtime because of the load they receive from us.
Is there a way to rate limit a specific task queue or even completely pause it?

One way that I thought of is just stopping the worker. But that means no active worker has the workflow registered. Is it an error to trigger workflows that aren’t registered by any worker? Or will that be fine?

[ryland]

I think this should help. Let me know if you still have questions.

Rate limiting task queues and workers

Hi, where can I read more about the options for rate limiting? I am interested in: rate limiting at the task queue level rate limiting at the worker level My understanding is that both are possible, but I must be missing something obvious. Thank you, Jacques

[maxim]

Look at the issue Ryland mentioned about rate-limiting the task queue.

Is it an error to trigger workflows that aren’t registered by any worker?

No, it is OK to start/signal/etc. workflows even if no worker is running. The same applies to activities. It is OK to schedule an activity without its worker running.