Create Resources Problem
This document will use the actual root cause analysis information to make a generic view that can be used if you run into the same or similar problem. Finally, the document will describe the situation, the problem, the analysis, and the result.
Should you have any questions, please get in touch with academy@emagiz.com.
1. Situation
The user observed that a resource in Create (definition) could not be opened by eMagiz as they were faced with a platypus that was loading infinitely. As a result, changes made in Design in both the definition and the transformation could never be actualized in Create and, therefore, not used in the data processing of messages.
2. Problem
The problem in this case was that the user needed help updating the definition (and accompanying transformation) and was stuck updating specific integrations within the data model.
3. Analysis
3.1 Reproduction
To reproduce the issue, we first looked at the client's model to see in Design, which changes were made recently that could explain why a definition could not be shown to the user. Given that we saw multiple changes, we reproduced the situation before and after these changes in a separate model. We found no structural defect in the synchronization between Design and Create.
Secondly, we removed the changes after consulting with the user to see what the effect would be. This worked in most cases. Afterward, we added the changes again, one by one and at a slow pace, and checked whether the Create definition was still visible after every change. This resolved the problem in most cases.
In some cases, though, we noticed that the synchronization issues were more problematic and could only be resolved by decoupling the definition and transformation from the flow in Create, deleting the resources under Create -> Resources, and reopening the flow. This process forces eMagiz to recreate the resources from scratch, forgetting about history. This solved the problem for the remaining cases.
3.2 Analysis
Our reproduction concluded that synchronization issues can occur between Design and Create. The highest chance these synchronization issues arise is when changes are made to a definition in rapid succession. To resolve those problems, the user must either remove the latest changes and add them back slowly or delete the resources in question from Create as described above. In all reported cases, one of the other was proven to be the solution.
4. Result
It is essential to pace yourself when altering definitions when working with definitions. This is mainly the cause when you add and delete the same attribute or entity quickly. There are two distinct ways of fixing these issues, as described above.