Solace - New message in topic trigger ​

The New message in topic trigger monitors one or more Solace topic subscriptions you specify for new messages.

Input ​

Input fieldDescription
TopicsEnter one or more topic subscriptions to listen on, for example, ['orders/created', 'orders/updated']. This field supports wildcards for single level (*) and remaining levels (>).
Message formatSelect the message format. Options are Binary and Text.

Output ​

Output fieldDescription
Acknowledgement handleAn opaque handle identifying this message for manual acknowledgement.
Message typeThe format of the received message payload. For example: text.
Delivery modeThe delivery mode the message was sent with. PERSISTENT messages are stored by the broker until delivered, acknowledged, or expired. DIRECT messages aren't stored and can be dropped if no subscriber is ready to receive them.
PriorityThe message's delivery priority. This only affects delivery order if the queue has priority ordering enabled.
Class of serviceThe message's class of service, which determines how readily the broker discards the message if its destination queue is congested.
DestinationThe queue or topic the message was delivered to. Contains:
  • Type
  • Name
Reply toThe destination to send replies to, if the sender set one. Contains:
  • Type
  • Name
Application IDThe sending application's ID, if set by the sender.
Application typeThe sending application's message type, if set by the sender.
HTTP content typeThe message's HTTP content type, if set by the sender.
Correlation IDAn identifier for tracking related messages, if set by the sender.
Sender IDThe identifier of the client that sent the message, if set.
Replication group IDThe message's replication group ID, used for Solace data replication.
Sequence numberThe message's sequence number, if set by the sender.
Sender timeThe sender's timestamp, in milliseconds, if set.
Receive timeThe timestamp when the message was received, in milliseconds.
Time to liveThe broker-enforced time-to-live the message was sent with, in milliseconds. This is what actually expires the message, and routes it to the dead message queue if it's eligible. 0 means the message doesn't expire.
ExpirationThe informational expiration timestamp header, in milliseconds, if set. Unlike Time to live, it doesn't expire the message on the broker.
Delivery countThe number of times this message has been delivered.
Is replyWhether this message is a reply to an earlier request, as used in Solace's request-reply messaging pattern.
Dead message queue eligibleWhether the message is eligible to be routed to the dead message queue if it can't be delivered.
Discard indicationWhether one or more messages were discarded before this one, for example, due to a full buffer.
Eliding eligibleWhether the message is eligible for eliding, where the broker thins a rapid series of updates to a topic down to only the latest value for a slow subscriber. Applies to direct messages only.
User dataArbitrary user data, base64-encoded, if set by the sender.
PropertiesThe message's custom properties. Contains:
  • Name
  • Type
  • Value
  • List size: The number of properties.
  • List index: The property's position in the list.

Last updated: