Managing subscriber states

Subscriber state indicates whether a subscriber is active or inactive. You can view and manage the state of a subscriber.

About this task

The states that can be set for a subscriber are Enable, Disable, and Suspend. You can change the state of a subscriber in the following scenarios.

The Messaging Provider system is functioning under an unusually heavy load.
The system to which subscribers interact needs maintenance or is becoming unresponsive.
The error occurs during message processing and the subscribers who are listening to the message are suspended automatically by the Messaging Provider system.

In this section, the steps are explained to change the subscriber state from the Events page. You can change the state of a subscriber by going to the Subscriber details page of a particular subscriber.

Procedure

Go to Events > Messaging.
The existing subscribers are listed.
Identify the subscriber for which you want to change the state and click the Overflow menu icon for the corresponding subscriber.
A menu is displayed.
Select the state that you want to set for the subscriber from the list of options that appear.
When you change the state of a subscriber, the system takes some time to update the change. During this time, new messages are retrieved and processed. Or, click the checkbox next to the Name in the header row to change the state of all subscribers at once

Results

You have changed the subscriber state. The following table explains the subscriber states:

Subscriber State	Behavior
Enabled	The subscriber is active to receive and process messages.
Enabled but not running	The subscriber is unable to connect to the Messaging Provider either because the account has been disabled or because the system is unable to reach the messaging provider. A warning icon is displayed near the state of the subscriber.
Disabled	The subscriber is not available and cannot receive and process any message. Note: Subscribers that are disabled can be enabled only by using the user interface.
Suspended	The subscriber is partially available. That is, the subscriber can process only existing messages but cannot receive any new messages. Note: Subscribers can enter the Suspended state due to one of the reasons: A user has suspended a subscriber explicitly by using the user interface. The system suspends a subscriber for reasons like message processing error, server overload, and backend system failure. In such cases, the subscriber is automatically enabled after the cause is addressed.
Not Configured	The subscriber is not configured, that is, it does not have any routing rules that are defined and is marked with an orange warning icon. You can configure the subscriber using the Edit option either from the Subscribers page or from the corresponding workflow.

The following are the key points to consider when changing the subscriber state:

When you disable an enabled subscriber, the system checks for existing and new messages. The existing messages that are being processed are allowed to complete, whereas messages that are awaiting to be processed are dropped and cannot be retrieved again. New messages are not retrieved.
When you suspend an enabled subscriber, the system allows existing messages that are being processed and messages that are awaiting to be processed to continue their normal course of execution. New messages are not retrieved.
If you disable an enabled subscriber that is associated with a queue, you can create a new subscriber on the same queue. This means, you can have only one active subscriber for a queue but can have multiple disabled subscribers for the same queue. This is applicable only for internal Messaging Providers.
If you want to enable a disabled subscriber that is associated with a queue, make sure that the queue is not associated with any other active subscriber. This is because there can be only one active subscriber for a queue.
You cannot suspend a disabled subscriber directly. If you want to suspend a disabled subscriber, you must enable it and suspend.