86f172218e
The log call sat behind the status guard, so it only ever fired for a connection that was not already in Error. The connection this commit was written for - 68 failed jobs, 3 sync-log rows - is parked in Error and stays there, so every one of the 65 missing deaths would have hit the guard and written nothing. Logging now happens as soon as the connection row resolves; the guards still own the status write, which is the part that must not clobber an earlier, better error message. |
||
|---|---|---|
| .. | ||
| Actions | ||
| Ai/Agents | ||
| Console/Commands | ||
| Contracts | ||
| Enums | ||
| Events | ||
| Exceptions/Banking | ||
| Features | ||
| Http | ||
| Jobs | ||
| Listeners | ||
| Mcp | ||
| Models | ||
| Notifications | ||
| Policies | ||
| Providers | ||
| Rules | ||
| Services | ||
| Support | ||