Skip to Content
Last modified by Erik Bakker on 2024/09/09 12:31
Show last authors
1 {{container}}{{container layoutStyle="columns"}}(((
2 The error flow is part of the default in any eMagiz project. This flow handles all errors that are thrown by (a)synchronous flows within your project and passes them through to the iPaaS, so they show up under Manage -> Error Messages. Recently we have made some changes to make the error flow work even more optimal.
3
4 Should you have any questions, please get in touch with academy@emagiz.com.=
5
6 == 1. Prerequisites ==
7
8 * Basic knowledge of the eMagiz platform
9
10 == 2. Key concepts ==
11
12 * The error flow is updated to make it more robust in handling unexpectedly large errors
13
14 == 3. Migration Path - Error flow ==
15
16 The error flow is part of the default in any eMagiz project. This flow handles all errors that are thrown by (a)synchronous flows within your project and passes them through to the iPaaS, so they show up under Manage -> Error Messages. Recently we have made some changes to make the error flow work even more optimal.
17
18 === 3.1 Legacy approach ===
19
20 In the legacy situation, the flow would determine whether or not message tracking was enabled for each message. Based on that, the error handling responded in a slightly different manner.
21
22 [[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--message-tracking-error-flow.png]]
23
24 === 3.2 New approach ===
25
26 In the new situation, the flow treats all messages the same and removes all headers to reduce the chance the error message will cause problems downstream for the iPaaS or the portal.
27
28 [[image:Main.Images.Migrationpath.WebHome@migration-path-emagiz-error-flow--clean-error-flow.png]]
29
30 === 3.3 How to get to the new approach ===
31
32 Migrating from the old to the new error flow takes several steps to make it work correctly. Below you will find all these steps. Follow them carefully to achieve the desired result.
33
34 1. Determine if you made any custom changes to the error handling
35
36 * If yes, continue with step 2
37 * If not, continue with step 4
38
39 2. Determine if these changes are still justified
40
41 * If not, continue with step 4
42 * If yes, continue with step 3
43
44 3. Write down all manual changes you still need
45 4. Navigate to Create
46 5. Right-click on the Error process and press Reset flow
47 6. Add the manual changes back to the flow (if there are any manual changes)
48 7. Test the flow
49 8. Verify your results
50
51 * If the result is the same, you are finished
52 * If changes exist, analyze them and make changes where necessary
53 Congratulations, you have successfully migrated the error flow to the new setup
54
55 == 4. Key takeaways ==
56
57 * The error flow is updated to make it more robust in handling unexpectedly large errors
58
59 == 5. Suggested Additional Readings ==
60
61 * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
62 ** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Event Streaming Connectors.WebHome||target="blank"]]
63 *** [[Asynchronous Error Handling (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-asynchronous-error-handling||target="blank"]]
64 * [[Error Flow (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22error+flow%22||target="blank"]]
65 )))((({{toc/}}))){{/container}}{{/container}}