From 93adaba322666288e8a57e99f16198d0b64bd052 Mon Sep 17 00:00:00 2001
From: TekH <h.tek@digitaldata.works>
Date: Thu, 16 Apr 2026 11:28:46 +0200
Subject: [PATCH] Update error message to omit result count in exception

Removed the count of existing results from the BadRequestException
message when invoking rec actions for a batch. The error now simply
states that results are already associated with the batch.
---
 .../RecActions/Commands/InvokeBatchRecActionViewsCommand.cs     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ReC.Application/RecActions/Commands/InvokeBatchRecActionViewsCommand.cs b/src/ReC.Application/RecActions/Commands/InvokeBatchRecActionViewsCommand.cs
index aa3b1ee..7f4a70c 100644
--- a/src/ReC.Application/RecActions/Commands/InvokeBatchRecActionViewsCommand.cs
+++ b/src/ReC.Application/RecActions/Commands/InvokeBatchRecActionViewsCommand.cs
@@ -21,7 +21,7 @@ public class InvokeRecActionViewsCommandHandler(ISender sender, ILogger<InvokeRe
         var any = await sender.Send(new AnyResultViewQuery(BatchId: request.References.BatchId), cancel);
 
         if(any)
-            throw new BadRequestException($"Cannot invoke rec actions for batch {request.References.BatchId} because there are already results associated with it. Count: {any}");
+            throw new BadRequestException($"Cannot invoke rec actions for batch {request.References.BatchId} because there are already results associated with it.");
 
         var actions = await sender.Send(new ReadRecActionViewQuery() { ProfileId = request.ProfileId }, cancel);