Custom code preprocessors temporarily disabled on Braintrust Cloud
minor- Started
- Nov 12, 8:21 PM EST
- Resolved
- Nov 15, 9:40 PM EST
- Duration
- 73h 20m
Braintrust's updates (3)
- identified · Nov 12, 8:21 PM EST
We have temporarily disabled custom code preprocessors across Braintrust Cloud while we work on fixing an ongoing issue with it. This may affect how conversations render in the Thread view, and the output of Topics facets and any scorers that rely on a custom preprocessor. Saved preprocessor code is unchanged and nothing has been deleted. Logging, querying, experiments, and all other functionality are unaffected, and no other regions are impacted. A fix is in progress and we expect to re-enable custom code preprocessors shortly.
- monitoring · Nov 14, 10:29 AM EST
We have deployed a fix for the issue affecting custom code processors and re-enabled them across Braintrust Cloud. We will continue monitoring closely for any recurrence.
- resolved · Nov 15, 9:40 PM EST
This issue has been resolved.
What our checks recorded
We checked Braintrust 576 times from Braintrust's start time to its resolution, once every five minutes. Every one of them reached Braintrust's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 160 ms, against 274 ms over the 24 hours before. Braintrust posted the incident at Nov 12, 8:21 PM EST.
Updates are Braintrust's own words from its status page (status: resolved); we never add an inferred cause.