From 53e3cf21a385574b015bc1fc0b1b8059bc37e806 Mon Sep 17 00:00:00 2001 From: Waleed Latif Date: Thu, 12 Nov 2026 21:55:42 -0800 Subject: [PATCH] chore(pii): drop the over-long text example from the mask client's outage comment Presidio now masks texts over spaCy's length limit instead of answering 500, so the comment names a failure that still produces a deterministic 500 --- apps/sim/lib/guardrails/mask-client.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/apps/sim/lib/guardrails/mask-client.ts b/apps/sim/lib/guardrails/mask-client.ts index ddd9199b08d..b1de4f2093f 100644 --- a/apps/sim/lib/guardrails/mask-client.ts +++ b/apps/sim/lib/guardrails/mask-client.ts @@ -92,8 +92,9 @@ function isRetryableChunkError(error: unknown): boolean { * Statuses that mean the service is down rather than that one request was bad: * the load balancer has no healthy target (502/503/504), or the mask-batch route * could not reach Presidio (503). A 500 is retried but never read as an outage — - * Presidio answers 500 for deterministic per-input failures too (an over-long text - * spaCy refuses), and one such chunk must not scrub the rest of the payload. + * Presidio answers 500 for deterministic per-input failures too (an input that + * raises inside a recognizer), and one such chunk must not scrub the rest of the + * payload. */ const OUTAGE_STATUSES = new Set([502, 503, 504])