---
schema_version: "1"
id: 8ed64f29333418a7f52937c416590caab715575ef1d8f7d4ee8ad63ba10c9ff9
title: System Interface Offline and Online Status
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_system_interface_offline_and_online_status_235977.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_system_interface_offline_and_online_status_235977.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f9682c2b3666027b4be074bfad82f9fa981ec087846e9f01b64b80bf2bde1375
description: If a fulfillment system is unresponsive, you can set the relevant system interface to Offline. Any callout that would otherwise try to communicate with that system is moved to the On Hold status instead.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# System Interface Offline and Online Status

If a fulfillment system is unresponsive, you can set the relevant system interface to **Offline**. Any callout that would otherwise try to communicate with that system is moved to the **On Hold** status instead.

For example, let's say that you have a number of callouts that normally send a request to a third party's `/activation` endpoint. One day, that company tells you that the activation system will be down for two hours of scheduled maintenance. Rather than have all of those callouts fail during those two hours, you can set the relevant system interface to **Offline**.

Doing so moves those callouts to the **On Hold** state. When the system goes back online, change the system interface back to **Online**. The callouts move to the **Ready** state where they're picked up and orchestrated as usual.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-order_management-264-0-0-production-enus/c2040b01-aade-4ba7-8a7d-d7cd745d5c8c/images/icon_note.png)

Note

For Offline and Online status to work, your org must be running in PlatformEvents mode. See [OM Standard: Platform Events for Orchestration](https://help.salesforce.com/s/articleView?id=ind.comms_t_om_standardplatform_events_for_orchestration_241449.htm&release=264.0.0&type=5 "Starting with the Spring '21 release, new Order Management Standard customers use the PlatformEvents mode by default, instead instead of BatchApex mode. Customers using (or upgrading from) earlier versions have to make a few changes.")

## Offline Status

- A callout is moved to the **On Hold** state only when it's either ready to execute or it's retrying a failed attempt. For example, if you've scheduled the callout to run later, then it remains in a **Scheduled** state until it's ready to run. Only then does it change to **On Hold** (if the system interface is still set to Offline).
- If an order amendment is submitted while a callout is on hold, then the callout is frozen, and then treated as any other frozen item.

## Online Status and the Integration Retry Job

The Integration Retry job is responsible for changing the state of a callout after its system interface is back online.

- The **Integration Retry** job checks callouts in the **On Hold** state to see whether their associated system interface statuses are set to **Online**. If so, then the job moves the callout to the **Ready** state.
- The **Integration Retry** job runs every minute by default, but you can edit the custom settings to change that setting, and others. See [Custom Settings for Integration Retry and System Interface Online Mode](https://help.salesforce.com/s/articleView?id=ind.comms_t_custom_settings_for_integration_retry_and_system_interface_onlinemode_237156.htm&release=264.0.0&type=5 "Order Management allows you to change the default settings for the job that retries callouts, or takes them online when you set their system interface online. The same job does both things, so changing the setting affects them both.")
- Before the **Integration Retry** job can run the first time, you "schedule" it. Scheduling the job just means clicking the **Start** button next to the **Schedule Integration Retry Job** option on the admin panel. See [Schedule the Integration Retry Job in Order Management Standard](https://help.salesforce.com/s/articleView?id=ind.comms_t_schedule_the_integration_retry_job_in_order_management_standard_237098.htm&release=264.0.0&type=5 "Start the Schedule Integration Retry Job from the Vlocity Order Management Admin Panel. After you've scheduled this job, it runs according to its custom settings. This job is relevant to retrying failed callouts, as well as moving a system interface to Online status.")

- **[Put a System Interface into Offline Status](https://help.salesforce.com/s/articleView?id=ind.comms_t_put_a_system_interface_into_offline_status_236030.htm&release=264.0.0&type=5)**  
    When a fulfillment system is down, you can set the status for that system interface to **Offline**. Doing so moves all callouts that call that system to the On Hold status.