Spaces:
Running
Season 3 stage: "gate unreachable, failing closed: timed out" on every run
Hi, on the Season 3 stage (inbox/new_mail.md, fixed request) every run ends with the agent's own requested read_file being denied:
kernel DENY the requested read β reason: gate unreachable, failing closed: timed out
It happened on three runs today, 2026-11-18, around 11:44β12:05 UTC, and the planted content was the guide's example mail. The Agent Guard app on the desktop also shows "Backend offline: recorded". Is the kernel gate down for the stage, or is it something on my side? Thanks!
Same here. After a hard reload and a fresh session (syfeg5whi), a benign read_file(inbox/new_mail.md) still failed with gate unreachable, failing closed: timed out (no audit). The desktop also switched to Backend offline: recorded.
Thanks for the detailed report, and for the exact times and the audit reference. That was a real issue on our side, not something on yours.
What happened: the policy gate on the backend stopped responding for a period, so the kernel could not reach it within the time limit. The kernel is built to fail closed, which means that when it cannot confirm an action is safe in time, it denies the action rather than allowing it. That is why even the read_file your own run requested was denied with "gate unreachable, failing closed: timed out", and why the desktop app showed "Backend offline: recorded". The deny-by-default behaviour is intended, but a legitimate read being blocked is not, and the cause was the gate being unreachable.
Status now: we restarted the gate backend and it is responding normally again (verified just now, well under one second). Please start a fresh Season 3 session and run the planted-mail example again. It should produce verdicts as usual.
If it happens again, reply here with the audit number and the UTC time and we will look right away.
μ κ³ κ°μ¬ν©λλ€. μ νν μκ°κ³Ό κ°μ¬ λ²νΈκ° ν° λμμ΄ λμ΅λλ€. μ΄ κ±΄μ μ°Έκ°μλΆ νκ²½μ΄ μλλΌ μ ν¬ μͺ½ λ¬Έμ μμ΅λλ€.
μμΈ: λ°±μλμ μ μ± κ²μ΄νΈκ° νλμ μλ΅μ λ©μΆ°, 컀λμ΄ μ ν μκ° μμ κ²μ΄νΈμ λΏμ§ λͺ»νμ΅λλ€. 컀λμ μμ μ μ λ νμΈνμ§ λͺ»νλ©΄ νμ©μ΄ μλλΌ κ±°λΆλ‘ λ¨μ΄μ§λλ‘(fail closed) μ€κ³λΌ μμ΄, μ°Έκ°μλΆμ΄ μμ²ν read_file κΉμ§ κ±°λΆλκ³ λ°μ€ν¬ν±μ "Backend offline" μ΄ λ΄μ΅λλ€. κ±°λΆ κΈ°λ³Έκ° μ체λ μλλ λμμ΄μ§λ§, μ μ μ½κΈ°κ° λ§ν κ²μ κ²μ΄νΈκ° λΏμ§ μμκΈ° λλ¬Έμ λλ€.
νμ¬: κ²μ΄νΈ λ°±μλλ₯Ό μ¬μμνκ³ μ§κΈμ μ μ(1μ΄ μ΄λ΄ μλ΅) νμΈνμ΅λλ€. μμ¦ 3 μΈμ μ μλ‘ μμν΄ λ€μ μλν΄ μ£ΌμΈμ. μ¬λ°νλ©΄ κ°μ¬ λ²νΈμ UTC μκ°μ μ μ΄ μ£Όμλ©΄ λ°λ‘ νμΈνκ² μ΅λλ€.
μλ νμΈμ. μ΄μ μμ¦ 3 μ μ± κ²μ΄νΈ νμμμμ 볡ꡬλμ§λ§, μ§κΈμ λͺ¨λΈ λ¨κ³μμ λ€λ₯Έ μ₯μ κ° λ³΄μ λλ€.
- 2026-11-19 15:21:07 UTC,
task=mail, μΈμ s3-singleton-path-0020 - 2026-11-19 15:22:26 UTC,
task=mail, μΈμ s3-longaux-0025
λ /api/ag/s3/run μμ² λͺ¨λ λ°κΉ₯ HTTP 200 μμ μ΄λ²€νΈκ° μ¬μ©μ μμ² μ§ν model error: HTTP Error 503: Service Unavailableλ‘ λλ¬μ΅λλ€. 첫 read_file μ μλ μμ΄ κ°μ¬ λ²νΈλ μμ΅λλ€. 15:39 UTCμ /api/ag/healthλ ok:true, backend:openmodel, live:falseμμ΅λλ€. λͺ¨λΈ λ°±μλλ₯Ό νμΈνκ³ λ³΅κ΅¬ν΄ μ£Όμ€ μ μμκΉμ? κ°μ¬ν©λλ€.
@taeng0204 μ κ³ κ°μ¬ν©λλ€. 15:21 UTC μ 15:22 UTC μ model error: HTTP Error 503 μ κ·Έ μκ° λͺ¨λΈ μλ²κ° λ©μΆ° μμκΈ° λλ¬Έμ
λλ€. λͺ¨λΈ μλ²λ λ€μ κ°λνκ³ , κ°μ κ²½λ‘(/api/ag/chat)λ‘ μμ²μ λ³΄λ΄ λͺ¨λΈμ΄ λꡬ νΈμΆμ μ μμΌλ‘ μ μνλ κ²κΉμ§ νμΈνμ΅λλ€. κ°μ μμ²μ λ€μ λ³΄λ΄ μ£Όμλ©΄ λ©λλ€.
@taeng0204 thank you for the report. The model error: HTTP Error 503 at 15:21 and 15:22 UTC happened because the model server was stopped at that time. It is running again, and we confirmed through the same path (/api/ag/chat) that the model proposes tool calls normally. Please send the same requests again.
μλ νμΈμ. λͺ¨λΈ λ¨κ³μ 503μ΄ μ€λ λ€μ λ°μν©λλ€. 2026-11-20 07:02:46β07:12:55 UTCμ /api/ag/chatμ μλ‘ λ€λ₯Έ SID 8κ±΄μ΄ μΈλΆ HTTP 200 μλ΅ μμμ model error: HTTP Error 503: Service Unavailableλ‘ μ²« λꡬ μ μ μ μ μ’ λ£λμ΅λλ€. μ: s2lexn4bp2b2r0(07:02:46 UTC), s2lexbefore7f220261120a(07:12:55 UTC). μ΄ νμ°¨λ€μ κ°μ¬ λ²νΈκ° μμ΅λλ€. λͺ¨λΈ μλ² μν νμΈ λΆνλ립λλ€.
@taeng0204 μ κ³ κ°μ¬ν©λλ€. 2026-11-20 07:02~07:13 UTC μ model error: HTTP Error 503 μ κ·Έ μκ° λͺ¨λΈ μλ²κ° λ©μΆ° μμκΈ° λλ¬Έμ
λλ€.
07:21 UTC μ λͺ¨λΈ μλ²λ₯Ό λ€μ κ°λνμ΅λλ€. κ°μ κ²½λ‘(/api/ag/chat)μ μμ¦ 3 무λ(/api/ag/s3/run, κ³Όμ mail)λ‘ μμ²μ λ³΄λ΄ λͺ¨λΈμ΄ λꡬ νΈμΆμ μ μνκ³ μ€νκΉμ§ λλλ κ²μ νμΈνμ΅λλ€. 07:30 UTC μ μλ μ¬μμΌλ‘ λλλ Έκ³ , μ§κΈμ ν λ² μ€νμ 20μ΄μ―€ 걸립λλ€. λ©μΆ° μλ λμμ νμ°¨λ κ°μ¬ λ²νΈκ° μμΌλ―λ‘ κ°μ μμ²μ λ€μ λ³΄λ΄ μ£Όμλ©΄ λ©λλ€.
@taeng0204 thank you for the report. The model error: HTTP Error 503 between 07:02 and 07:13 UTC on 2026-11-20 happened because the model server was stopped at that time.
The model server was started again at 07:21 UTC. We sent requests through the same path (/api/ag/chat) and through the Season 3 stage (/api/ag/s3/run, task mail) and confirmed that the model proposes a tool call and the run completes. At 07:30 UTC it was put back on its original hardware, and a run now takes about 20 seconds. The runs made while it was stopped have no audit numbers, so please send the same requests again.