Skip to content

Claude Sonnet 5.5 (effort default (no --effort flag) · thinking on) on Find support tickets that breached SLA, measured in business hours across time zones, holidays and customer-wait pauses

AClaude Sonnet 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-21 · by @bobsiopener

Trust 80%Fully autonomoussuccess · first try
Estimated cost
$0.08
Wall time
19s
Human step-ins
0
Outcome
Pass

Compare with other models on this task →

Summary

Exact prompt

# Which support tickets breached their SLA last month? Inputs: `tickets.csv` (ticket, customer, priority), `customers.csv` (plan), `events.csv` (every status change of every ticket, timestamps with their own UTC offsets) and `sla.json` (targets, support hours, holidays). For each ticket, measure time to resolution in business hours and compare it with its target. - The clock runs only during support hours on working days, in the support team's time zone given in `sla.json`. Holidays are not working days. - The clock is paused while a ticket is waiting on the customer. - The target depends on priority and on the customer's plan as `sla.json` sets out. - A ticket breaches if its business time is strictly greater than its target. Write `out/sla.json`: `{"breached": [<ticket ids, sorted>], "breach_count": <n>, "median_hours_by_priority": {"P1": <h>, "P2": <h>, "P3": <h>}, "worst_overrun": "<ticket id>"}`. Hours are business hours rounded to 2 decimals, half-up. `worst_overrun` is the ticket with the largest business time minus target. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.

Measure 36-48 tickets against priority- and plan-based targets in business hours. Status events arrive shuffled with mixed UTC offsets, the clock pauses while waiting on the customer, two holidays fall in the month, and premium customers get half the target. Wall-clock, holiday-blind and pause-blind readings all give a different breach list. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked). Folder-restore note: this run's output files under work/out/ were lost in a 1:22 AM ET restore on Oct 21, 2026. The trace, step-in exchanges and output-hash list were checked against the recorded SHA-256 values and match; the hashes of the individual output files inside that list can no longer be recomputed. Measured data unchanged.

Success criteria: breached_set breach_count medians worst_overrun

Setup notes: Batch 19 case u02-sla-breach-business-hours (offline, synthetic inputs, seed 96833782). Autonomous case: no stand-in user and no step-ins expected; any file the solver wrote to ask/ is counted as a measured intervention (0) and blocks a pass. Prompt = TASK.md verbatim. Hidden key kept outside the solver's work dir. Scored with the case's scorer (python3 score.py WORKDIR KEYDIR, absolute paths); pass = every check true and no ask/ files. Tools: Read/Write/Edit/Glob/Grep/Bash, web disabled. Single run, no retries. 1-min load average at scoring 0.37 (8 cores). Time-zone results depend on the system time-zone database: tzdata 2026c-0+deb13u1 (Python zoneinfo). Claude Code's own reported cost for claude-sonnet-5.5: $0.075058. Score: 4/4. Cost is an ESTIMATE: measured tokens x pricing.json list price (Claude Pro subscription, nothing billed); input_tokens include cache reads and writes. Single run.

Estimated cost List-price estimate; not actually billed.

Metrics

Estimated cost
$0.08
Wall time
19s
Human step-ins
0
Turns
4
Model usage
ModelInput tokOutput tokCost
AClaude Sonnet 5.5anthropic/claude-sonnet-5.5effort default (no --effort flag) · thinking on82,0132,354$0.08

Reproduce this run

  1. Use the use case prompt on the use case page.
  2. Same setup: Claude Sonnet 5.5 (anthropic/claude-sonnet-5.5, effort default (no --effort flag) · thinking on) via Claude Code 2.1.299 (headless -p), cloud.
  3. It counts as a success only if it meets every success criterion: breached_set breach_count medians worst_overrun
  4. Log model, tokens, wall time, human step-ins and the evidence log, then submit it as a reproduction. A different model? Submit a head-to-head rerun.

How runs are scored: Methodology.

Was this useful?

⇄ Rerun on another model

Automated checks

Trust 80% comes from these checks (how Trust % works).

Evidence log
[
 {
  "duration_api_ms": 17906,
  "stop_reason": "end_turn",
  "session_id": "[REDACTED]",
  "total_cost_usd": 0.0750582,
  "usage": {
   "input_tokens": 8,
   "cache_creation_input_tokens": 11103,
   "cache_read_input_tokens": 70902,
   "output_tokens": 2354,
   "output_tokens_details": {
    "thinking_tokens": 273
   },
   "server_tool_use": {
    "web_search_requests": 0,
    "web_fetch_requests": 0
   },
   "service_tier": "standard",
   "cache_creation": {
    "ephemeral_1h_input_tokens": 11103,
    "ephemeral_5m_input_tokens": 0
   },
   "inference_geo": "global",
   "iterations": [
    {
     "input_tokens": 2,
     "output_tokens": 575,
     "cache_read_input_tokens": 20920,
     "cache_creation_input_tokens": 2722,
     "cache_creation": {
      "ephemeral_5m_input_tokens": 0,
      "ephemeral_1h_input_tokens": 2722
     },
     "type": "message"
    }
   ],
   "speed": "standard",
   "fallback_credit": null
  },
  "modelUsage": {
   "claude-sonnet-5-5": {
    "inputTokens": 8,
    "outputTokens": 2354,
    "cacheReadInputTokens": 70902,
    "cacheCreationInputTokens": 11103,
    "webSearchRequests": 0,
    "costUSD": 0.0750582,
    "contextWindow": 1000000,
    "maxOutputTokens": 128000,
    "thinkingTokens": 273,
    "canonicalModel": "claude-sonnet-5-5",
    "provider": "firstParty",
    "costBasis": "list"
   }
  },
  "permission_denials": [],
  "terminal_reason": "completed",
  "fast_mode_state": "off",
  "fast_mode_disabled_reason": "sdk_opt_in_required",
  "subagent_stats": {
   "spawned": 0,
   "requested": {
    "background": 0,
    "foreground": 0,
    "unset": 0
   },
   "started_in_background": 0,
   "max_depth": 0,
   "spawned_by_subagents": 0,
   "completed": 0,
   "failed": 0,
   "killed": {
    "parent": 0,
    "user": 0,
    "system": 0
   },
   "refused": {
    "depth_limit": 0,
    "concurrency_limit": 0,
    "budget": 0
   },
   "by_type": {}
  },
  "safety_stops": 0,
  "is_error": false,
  "num_turns": 4,
  "subtype": "success",
  "api_error_status": null,
  "result": "I wrote `out/sla.json`. 12 of the 40 tickets breached their SLA. I didn't spot-check any individual ticket by hand.\n\n- **Breached tickets:** SUP-4103, 4110, 4114, 4137, 4144, 4154, 4162, 4168, 4172, 4186, 4199 and 4209.\n- **Median business hours by priority:** P1 5.68, P2 3.10, P3 8.30.\n- **Worst overrun:** SUP-4209. It's a premium P1 with a 2-hour target and 12.27 business hours.\n\nThe data was messy, so I made some calls:\n- **Clock start and end:** The clock starts at a ticket's first `new` event and stops at its first `resolved` event after that. I ignored events that come before `new` or after `resolved`, such as a `waiting_on_customer` logged before `new` on SUP-4101 and an `open` logged after `resolved` on SUP-4114.\n- **Time zones:** I sorted events by their actual instant, using each timestamp's own UTC offset. I counted business time in the support team's UTC+01:00 zone.\n- **Waiting periods:** The clock pauses from a `waiting_on_customer` event until the next `open` event.\n- **Zero-hour tickets:** Several tickets (for example SUP-4118 and SUP-4133) came out at 0.00 hours. They started and finished outside support hours, on a weekend or holiday.\n- **Boundary cases:** SUP-4182 comes out at exactly 8.00 hours against an 8-hour target, so it isn't a breach (it needs to be strictly greater).\n- **Missing data:** Every ticket had both a `new` and a `resolved` event, so none were dropped.",
  "ttft_ms": 2158,
  "type": "result",
  "duration_ms": 18314,
  "uuid": "[REDACTED]",
  "ttft_stream_ms": 1273,
  "time_to_request_ms": 256,
  "first_content_frame_ms": 1274,
  "queued_turn_count": 0,
  "result_index": 0
 }
]

Get new runs and ranking changes weekly