Process the unprocessed messages from Service Bus queues/topic subscription using Automated tasks
  • 05 Apr 2021
  • 2 Minutes to read
  • Dark
  • PDF

Process the unprocessed messages from Service Bus queues/topic subscription using Automated tasks

  • Dark
  • PDF

Article Summary

Process left-behind/unprocessed messages from Service Bus queues/topic subscription using Automated tasks

We discussed how users could monitor for left behind messages in their Service bus queue/topic subscription in our previous Use case docs. Though we have already addressed that challenge, processing these left behind messages is also a concern. Serverless360 has got out of the box message processing capability that a user can leverage to process their left behind Service bus messages without any manual intervention.


When we build an Integration solution involving the Azure Service Bus, message flow plays a vital role. Applications connected with Service Bus Queue/Topic Subscription will pick up the messages and process them as defined. These are the most frequently made configurations with serverless architectures. There may be scenarios where our backend application may not be available for processing, and the messages can get stagnated in the Queue/Topic Subscription for a long time. Such situations will impact the business when the stagnated messages are left unattended. With Serverless360, we can inform the user about the left behind messages. And whenever Serverless360 announces any left behind messages, the next step will be to process these messages with the appropriate actions.


To process the left behind messages, user can use the operational capabilities that Serverless360 offers for Service Bus. User can retrieve messages and reprocess them by resending the message to a different destination. User can retrieve the left behind messages and resubmit them when the backend application is available for processing.
resubmit a message.png

resubmit message window.png

Suppose a user has a failover system implemented in their business process. In that case, the user can also resubmit the messages to their failover system using the resubmit to an Api destination option.

Sometimes, the left behind messages due to TimeToLive Expiry can get into the dead-letter queue. Serverless360 can help users to process the DDL messages as well. User can filter DDL messages with the error reason and resubmit/delete them.

resubmit a DDL message.png

If the user does not want to process the messages manually, Serverless360 has also got an automated task to process the messages regularly. Let us assume our goal here is to process all the left behind messages at the end of every day. With Serverless360, user can configure an automated task to run at a specific time of the day. So, now user can configure the time frame as shown below.

Automated tasks-DDL.png

User can schedule the automated tasks in Serverless360 with the following options:

  • Initiate process after save
  • Start time (when to initiate the automated task)
  • Schedule selected days to perform the automated task
  • Select the hours of the days to perform the automated task
  • Restriction on recurrence either by the number of occurrences completed or by the end date.

When the automated tasks process the messages, there is still a chance that our backend application is down. So, at that time, messages can be lost sometimes. For any business, every message is critical. So, no compromise for the message loss. That is why Serverless360 comes up a backup on your Service bus messages which are being resubmitted.

This is how Enterprise customers of Serverless360 achieve 100% processing of the incoming messages utilizing the toolsets offered by Serverless360.

Was this article helpful?