From 72b89da9c526c347c566f97623afee19be0f3ac1 Mon Sep 17 00:00:00 2001
From: Carlos Santos <4a.santos@gmail.com>
Date: Wed, 30 Jul 2025 12:51:02 +0200
Subject: [PATCH] frontend: enhance error handling for recording start requests

---
 .../src/lib/pages/meeting/meeting.component.ts         | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/frontend/projects/shared-meet-components/src/lib/pages/meeting/meeting.component.ts b/frontend/projects/shared-meet-components/src/lib/pages/meeting/meeting.component.ts
index 3f0ed3c..3ec8daa 100644
--- a/frontend/projects/shared-meet-components/src/lib/pages/meeting/meeting.component.ts
+++ b/frontend/projects/shared-meet-components/src/lib/pages/meeting/meeting.component.ts
@@ -395,8 +395,14 @@ export class MeetingComponent implements OnInit {
 	async onRecordingStartRequested(event: RecordingStartRequestedEvent) {
 		try {
 			await this.recManagerService.startRecording(event.roomName);
-		} catch (error) {
-			console.error(error);
+		} catch (error: unknown) {
+			if ((error as any).status === 503) {
+				console.error(
+					"No egress service was able to register a request. Check your CPU usage or if there's any Media Node with enough CPU. Remember that by default, a recording uses 4 CPUs for each room."
+				);
+			} else {
+				console.error(error);
+			}
 		}
 	}