From time to time the APIWORX team performs scheduled maintenance to apply security updates, scale infrastructure, deploy new features, or rotate components that support the integration runtime. When that happens we publish a maintenance notice in advance so internal admins can plan around the window. Notices typically include the date, the maintenance window in UTC, the services that may be temporarily unavailable, and any operational steps you should take before or after the work begins.
During a maintenance window, scheduled jobs may be paused, webhook delivery can be delayed, and customer portal access may be briefly unavailable. APIWORX is designed to recover automatically: queued events are retried, and webhooks that arrived during the window are re-delivered once the platform comes back online. If a workflow appears stuck after maintenance ends, check the jobs and transactions views for the affected connector and confirm the event timeline shows successful retries before opening a ticket.
If you operate critical month-end processes, marketplace cutovers, or trading-partner deadlines, share your blackout windows with the APIWORX team in advance. We will avoid scheduling planned maintenance in those windows whenever possible. For unplanned incidents, the same notice channel is used to communicate detection, scope, mitigation, and recovery so your team is never guessing what is happening on our side.
What to keep in mind
- Maintenance notices include start time, expected duration, and affected services.
- Queued events and webhooks are retried automatically once the window closes.
- Use the jobs and transactions views to confirm recovery before escalating.
- Share blackout windows so we can avoid them when scheduling planned work.