Take a cycler out of service for planned work
Open a service event, taking every channel on the cycler out of service.
One call replaces taking each channel out individually: calibration is performed on the instrument, so the whole cycler goes down as one event and comes back as one. Channels already out of service keep their existing incident (a broken relay is more specific than “being serviced”).
Rejected with 409 if the cycler already has an open event, or if any channel still has a running measurement.
Path Parameters
Body
The body is of type Raw Data · object.
Response
Successful Response
One instrument-level service on a cycler.
A service event is the thing a channel incident belongs to when the whole
cycler is down. Calibration is performed on the instrument, so a
40-channel cycler going in for its annual calibration is one event, not 40
unrelated outages that happen to share a category. Channel incidents opened
for the event carry its id in service_event_id, which is what lets one
action close them together.
At most one event per cycler may be open (performed_at null) — a unique
partial index enforces it, so "the current service" is a single unambiguous
row and the open-event write path is safe to retry.
Unique identifier for the service event
Organization this service event belongs to.
Project that owns the cycler (pinned to it by FK)
The cycler being serviced
What kind of work this is
calibration, preventive_maintenance, firmware, repair, other Timestamp when the event row was created
Timestamp when the event row was last updated
When the visit is booked. Required while the event is open; null is allowed on an event recorded after the fact.
When the service was actually done. Null means the event is still open — at most one such event per cycler.
Free-text detail about the service
User who opened or recorded the event
User who recorded the service as done