You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: downgrade queue size limit errors to warnings
Queue limit ServiceValidationErrors were being logged at error level,
consuming ~1.37M Sentry events/week (66% of total budget). These are
expected validation rejections, not bugs.
- Add logLevel property to ServiceValidationError (webapp + run-engine)
- Set logLevel: warn on all queue limit throws
- Schedule engine: detect queue limit failures and log as warn
- Redis-worker: respect logLevel on thrown errors
refs TRI-7911
Copy file name to clipboardExpand all lines: apps/webapp/app/v3/services/batchTriggerV3.server.ts
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -249,7 +249,9 @@ export class BatchTriggerV3Service extends BaseService {
249
249
250
250
if(!queueSizeGuard.isWithinLimits){
251
251
thrownewServiceValidationError(
252
-
`Cannot trigger ${newRunCount} tasks as the queue size limit for this environment has been reached. The maximum size is ${queueSizeGuard.maximumSize}`
252
+
`Cannot trigger ${newRunCount} tasks as the queue size limit for this environment has been reached. The maximum size is ${queueSizeGuard.maximumSize}`,
0 commit comments