Asynchronous Error Handling
In this microlearning, we will explain the basics of asynchronous error handling that plays a vital role in ensuring that messages that do not meet the criteria are correctly displayed in the Manage phase.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Prerequisites
- Basic knowledge of the eMagiz platform
2. Key concepts
This microlearning centers around asynchronous error handling for messaging flows in eMagiz.
By asynchronous error handling, we mean The process that receives and processes error messages to show to the user in Manage.
The asynchronous error handling has three relevant parts:
- All asynchronous queues come with a standard error handling on flow level
- The centralized error flow receives and processes these messages
- Each error message is sent via the internal eMagiz architecture to display it in Manage
3. Asynchronous Error Handling
Asynchronous error handling plays a vital role in ensuring that messages that do not meet the criteria are correctly displayed in the Manage phase.
The asynchronous error handling has three relevant parts:
- All asynchronous queues come with a standard error handling on flow level
- The centralized error flow receives and processes these messages
- Each error message is sent via the internal eMagiz architecture to display it in Manage
3.1 Error Handling Queues on Flow level
In asynchronous messaging, each flow that starts with a component that reads data from a queue comes with the standard error handling functionality in eMagiz. This error handling is illustrated by eMagiz in the form of a green dot with a red line. This part of the process ensures that each error is directly pushed to our infrastructure for processing.
3.2 Internal eMagiz Error processing
From here on out, a centralized instance consumes these messages. This instance processes all metadata and error messages coming in from all the projects created within eMagiz. This process ensures to properly store the data in the right place within our architecture. After it is stored, a user can view the information via the Manage phase. In the Manage phase, you will see a Dashboard that shows (on a flow level) all error messages that occurred within a specific time frame. If you want to learn more about this dashboard, please check out this microlearning.
These two parts ensure that when you handle your messages asynchronously and the message is placed on the queue, the message will either be successfully delivered to the external system or will end up in Manage as an Error Message.
4. Key takeaways
- All asynchronous queues come with a standard error handling on flow level
- The centralized error flow receives and processes these messages
- Each error message is sent via the internal eMagiz architecture to display it in Manage
5. Suggested Additional Readings
If you are interested in this topic and want more information, please read the help text provided by eMagiz.