Page MenuHomePhabricator

Investigate disparities between Evaluator and Orchestrator HTTP Status Codes
Closed, ResolvedPublicSpike

Description

We are now returning real status codes from both services but they don't seem aligned, i.e. I've seen hundreds of 429's coming from the Evaluator and I'd expect to see this in the Orchestrator logs in the very least but were not there.

Additionally, we need to decide on how we officially (at least for now) want the Orchestrator to be responding to Evaluator errors based on the status codes, not just error messages as previously. We can devise a plan as a wrap-up to this task and create a followup afterwards.

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptOct 15 2025, 10:20 PM
ecarg triaged this task as Medium priority.Oct 15 2025, 10:21 PM
ecarg added a project: Essential-Work.
DSantamaria changed the task status from Open to In Progress.Nov 12 2025, 7:00 AM

I've since added logs to show if/where the rate-limiting middleware was rate-limiting the requests from the Evaluator and confirm that that mystery is solved. Evaluator errors have also since been initiated.

Jdforrester-WMF subscribed.

Oops, moving this to the correct column re-opened it. I've switched off the trigger.