Start integrating with ONEiO for free!
SIGN UP

Identifying and Managing an Inbound Queue

Introduction

This article explains how to identify, investigate, and manage inbound queues for endpoints showing a warning state in the Home View. It walks through accessing queue details, reviewing queued messages, suspending the affected endpoint, and safely removing messages from the inbound queue.

 

Overview
 

  1. Step 1: Access the Endpoint Details
  2. Step 2: Open the Inbound Queue Details
  3. Step 3: Manage Inbound Queue Messages
  4. Step 4: Suspend the Endpoint 
  5. Step 5: Remove Queued Messages

     

Identifying an Inbound Queue

In the Home View, an endpoint displaying a warning state indicates that it has either an inbound or outbound queue

 

Step 1: Access the Endpoint Details

Click the endpoint displaying the warning state to open the Endpoint Status Details view.

In this view, you can identify whether the issue is caused by an inbound queue or an outbound queue.

For both cases, we display: 

  • Queue Count - the number of queued messages; 
  • Oldest Message - how long the last message has been in the queue 
  • and Oldest Message Timestamp - When the oldest message entered the queue


Step 2: Open the Inbound Queue Details

Click the iconto open the inbound queue details:

 

The inbound queue details page displays:

  1. Part of the content of the oldest message in the queue, how long the message has been queued (meaning how long the endpoint has had a queue), and the timestamp showing when the message was received from the inbound instance by ONEiO.
  2. A summary of the queue, including the total queued messages and the number of queued messages grouped by entity

After reviewing the queue details, you can manage the queue by selecting Manage Inbound Queue Messages.


Step 3: Manage Inbound Queue Messages

When managing the inbound queue messages, you will be allowed to remove only the oldest message in the queue, or, if you prefer, remove all messages from the inbound queue.

Before queue management can begin, the endpoint must be suspended. Suspending the endpoint only affects the selected endpoint and does not impact other endpoints.


Step 4: Suspend the Endpoint 

When selecting Manage Inbound Queue Messages, you will be prompted to suspend the endpoint:

Edit the endpoint, select the suspended status as shown below, and save the endpoint.

 

Step 5: Remove Queued Messages

After suspending the endpoint, return to the Home View and access the queue management again by repeating steps 1 to 3

When managing an inbound queue, you have the following options:

  1. Delete only the oldest message in the queue 
  2. Delete all messages from a specific entity 
  3. Delete all messages from all entities in the inbound queue


In the example below, all inbound queue messages are selected for removal. The oldest queued message is automatically selected by default.


After clicking Delete, a confirmation alert will appear once the selected messages have been successfully removed from the inbound queue.

 

Important

After completing the process, re-enable the endpoint. Suspended endpoints continue receiving inbound messages, but they stop sending outbound messages while suspended.

 

A note on suspended endpoints

Queue alerts cover all endpoints in your subscription, including suspended ones. This is deliberate. An endpoint suspended by accident will still receive inbound messages, and the queue will start building silently. The alert makes sure you notice. 

If you’re seeing queues build up on a suspended endpoint, that’s a signal: either the endpoint shouldn’t be suspended, or the sending system needs to stop routing messages to it. The cleanest fix is to delete the endpoint entirely so messages have nowhere to land.

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.