From 83bd6236fbec9294cab860bab2416a030fc1c9af Mon Sep 17 00:00:00 2001
From: Joe Caputo <joseph.caputo@amplica.io>
Date: Fri, 16 Aug 2024 11:41:13 -0400
Subject: [PATCH] fix: resume queue in content-publishing when Capacity is
 available (#393)

# Description
Resume queue when Capacity is available (was logging event, but not
resuming queue)

# Acceptance Criteria
- [x] Publishing queue is resumed when Capacity becomes available

Closes #392
---
 .../apps/worker/src/publisher/publishing.service.ts              | 1 +
 1 file changed, 1 insertion(+)

diff --git a/services/content-publishing/apps/worker/src/publisher/publishing.service.ts b/services/content-publishing/apps/worker/src/publisher/publishing.service.ts
index b8aecd78..41793fba 100644
--- a/services/content-publishing/apps/worker/src/publisher/publishing.service.ts
+++ b/services/content-publishing/apps/worker/src/publisher/publishing.service.ts
@@ -112,6 +112,7 @@ export class PublishingService extends BaseConsumer implements OnApplicationBoot
     if (await this.publishQueue.isPaused()) {
       this.logger.debug('Received capacity.available event');
     }
+    await this.publishQueue.resume();
     try {
       this.schedulerRegistry.deleteTimeout(CAPACITY_EPOCH_TIMEOUT_NAME);
     } catch (err) {