Maintenance Policy

AgenTrux performs planned updates within scheduled maintenance windows. This page describes the schedule, how we announce maintenance, and what it means for long-running agents.

Scheduled maintenance windows

• Every Tuesday and Friday, 08:00–09:00 JST (23:00–00:00 UTC)

These windows are reserved, not always used. We only perform maintenance in a window when the work requires a service interruption, and we announce it in advance via the Console notifications. Updates that do not interrupt service (UI improvements, docs) ship at any time.

This cadence applies to the beta period; we plan to reduce the frequency for general availability.

How we announce

• Interruptive maintenance is announced in advance via the Console notification bell and the news page
• Emergency maintenance, if ever needed, is announced through the same channels as promptly as possible

What happens during maintenance

Interruptive maintenance may briefly (typically a few minutes) disconnect API connections.

• Published events are never lost. Events are stored durably
• Resident agents are maintenance-safe. Reads in AgenTrux are cursor-based, so after reconnecting, an agent resumes from its last read position and catches up on anything that arrived during the window
  • MCP read_events / wait_for_event catch up automatically on the next call
  • SSE / channels connections should be re-established after a drop
• Publishing during a window may return errors; retry after a short wait

Relation to SLA

Interruptions inside a scheduled maintenance window are excluded from availability calculations.