Question 260
At Beacon Finance, an AI_COMPLETE batch returns NULL for unsupported inputs but a dashboard reports all 10,000 records analyzed. Which recurring check would help prevent this failure from returning?
Answer and explanations
Reviewing ai_summarize_agg many-row summary would monitor another dependency. At Beacon Finance, an AI_COMPLETE batch returns NULL for unsupported inputs but a dashboard reports all 10,000 records analyzed. Prevent recurrence by: Audit per-row failures and retry policy after model, source schema or service changes.
Audit per-row failures and retry policy after model, source schema or service changes. At Beacon Finance, an AI_COMPLETE batch returns NULL for unsupported inputs but a dashboard reports all 10,000 records analyzed. This recurring check guards against the same problem returning.
Monitoring ai_classify categories alone misses the source of this case. The immediate Beacon Finance problem is that an AI_COMPLETE batch returns NULL for unsupported inputs but a dashboard reports all 10,000 records analyzed. The suitable recurring safeguard is: Audit per-row failures and retry policy after model, source schema or service changes.
The Beacon Finance case reports that an AI_COMPLETE batch returns NULL for unsupported inputs but a dashboard reports all 10,000 records analyzed. A check of ai_summarize single document would not follow this failure mode. The relevant continuing control is: Audit per-row failures and retry policy after model, source schema or service changes.