Start integrating with ONEiO for free!

Message Feed


The message feed is a real-time view of the message flow in your subscription. You are able to monitor the traffic and/or search for messages with a ticket ID. The feed consists of three steps; received message (inbound), message processing (ONEiO), and message(s) sent out (outbound). 

  1. Message search functions
    • You can search for messages with the ID of the ticket. This ID can be any of the IDs included in the integration.
  2. Message timestamp
    • Timestamp when the inbound message has been received by ONEiO
  3. Inbound message/message received
  4. Rule(s) applied
  5. Outbound message(s) / message(s) sent
  6. Message Feed pause button
    • Click to pause/start the loading of the message
    • Scrolling will automatically pause the feed
    • Clicking on any message will pause the feed
    • The message feed will still be updated just no new messages will be loaded into the UI


Details of messages

When clicking the message line from the feed, the message details are shown.

On the left, the attributes of the inbound message are shown. These depend on the attributes mapped in the matched Routing Rule and not on what is present in the incoming payload.
If no attributes are mapped in the Routing Rule no attributes will be shown.
If there are no Routing Rules matched, the first 15 attributes of the inbound payload are shown.

Also, the current values of any conversation variables that are set, are visible here. As are the received attachments.



Message attributes

By default, the first 15 attributes are visible in the view. Selecting "See all" shows all attributes in this message. You can use the filter to search for attributes.


It is possible to search for an attribute or value through the search function. 


Conversation Variables

Conversation variables before the rule is run are visible in a separate tab under inbound message. Values after are shown under outbound message. ONEiO__xONEiO_Demo_-_Enterprise__4_.png


Received attachments are shown in a separate tab under inbound message. Sent attachments are shown under outbound message. 


Inbound and outbound messages in this view are logical events. Depending on the endpoint type, a single message can contain multiple actions. There can be attachment downloads and uploads or lookups of different kinds.  You can see the details of each event by clicking See Details -button

Synchronous responses

It is possible to use a synchronous response the same way as an inbound message. However, responses to the outbound messages are directly visible in the message feed only when there is a rule configured to handle it. The result of the response is seen in the message that has originally sent the message out. This shows if the message has been acknowledged successfully, or has ended up in an error. Note, that the response handling is represented from right to left in the feed.  


Searching for messages

You can search for messages by inserting a ticket id into the search field.


Inbound message reprocessing

With ONEiO it is possible to reprocess the inbound message in case anything didn't go as planned. In this example, the CREATE rule was misconfigured and did not trigger on the received CREATE message.


Usually, this would mean that the message would need to be resent from the source system. But with ONEiO you can reprocess that message without the need to resend it.

Clicking the Reprocess Inbound Message button under the message submenu and confirming your choice in the Reprocess Modal forces the original message through our inbound adapter just like it would with a new message.



The notification on the top of the UI shows that the reprocessing has been successfully initiated.


The reprocessed message is visible in the message feed as a new message with the initial message just below.



There are two types of errors when sending messages out from ONEiO; recoverable and unrecoverable errors. What error is considered recoverable and what is not, depends on the endpoint and in some cases on the opinion of the user. F.ex. in some cases HTTP 403 Invalid Grant could be interpreted as recoverable and in other cases not. You can configure these in Endpoint configurations with Unrecoverable HTTP error codes.


Recoverable errors (orange)

Recoverable errors are errors that are normally resolved with the recovery of an external party. These errors are typically communication or IO-related, e.g. network outages, bad credentials, etc. In case of recoverable error, ONEiO will automatically retry to send the message. While the message is in a retry loop, all following messages toward the same endpoint are queued. If the error goes away, the message is sent and the next message will be processed.

Canceling messages

It is possible to cancel a message that is currently in the retry loop. The cancel function can be found from the menu in the message view if the message is in a cancelable state.


From the menu choose "Cancel Outbound Message"


And confirm your selection.



Unrecoverable errors (red)

Unrecoverable errors are errors that should not be retried. In a case of an unrecoverable error, the handling will fail immediately and the next message towards the endpoint is processed. These errors will automatically create an alert to all recipients of alert emails.

It is possible to resend a message that has failed to an unrecoverable error. Resend function can be found from the menu in the rule.

If you need more information on Errors and Warning please read our article on Notifications 

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


  • The phrase "These are also known as "Send attributes" and display all attributes that are send outbound." under "Conversation attributes" looks like it's in wrong place.

    Comment actions Permalink
  • Hi Tero,

    Yes you are right. There is in fact an image missing that sentence belongs to. We are updating the UI guide soon as new features have been released.

    Comment actions Permalink
  • Why do you only allow the search to be based on Ticket ID?

    It would be great if you could add more advanced filtering.

    Comment actions Permalink
  • Can we doing Filtering on endpoints? or routing Rules?

    Comment actions Permalink
  • It would also be useful if we could filter on just errors, pending, or queued.

    Comment actions Permalink
  • Can we cancel multiple outbound messages at a time ?

    Comment actions Permalink
  • Hi,

    There are now new filters available in the Advanced Message Feed to filter on endpoints, routing rules, use cases, as well as statuses.

    Jagadeesh, we will look into adding the option to cancel multiple outbound messages. Currently, it is not available.

    Comment actions Permalink

Please sign in to leave a comment.