Changes for page Introduction

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -50,7 +50,16 @@
50	50
51	51	With all this information you should be able to solve 99% of all the **flow** related support tickets.
52	52
	53	+In case of a **runtime level** problem the following overviews are most interesting when analyzing the ticket:
53	53
	55	+* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message||target="blank"]]
	56	+** In here you can view statistics on runtime level. Here you can see whether a runtime is actually sending metrics and whether it is/was in trouble. This way you can easily see whether the runtime has a configuration or memory problem.
	57	+* Logging
	58	+** Once you have identified that a runtime is/was in trouble you can search for corresponding Error or Warning logs on runtime level. These shed additional light on why the runtime is in problem.
	59	+
	60	+Should Manage not provide you the answers it becomes time to challenge the assumptions of the client on the problem. This can be done with the help of the Deploy phase ()
	61	+
	62	+
54	54	First, you should check the assumptions of the person coming to you with a ticket. This is for both the Create and the Deploy phase of eMagiz. In Deploy, you check which version of a flow is running and whether this matches the client's expectations. Once you have established the correct flow version, it could happen that what is running is not what a user expected. The first step is to eliminate this mismatch.
55	55
56	56	If the flow version is as expected, we can check the [[properties>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] to see whether we see any changes. In this situation, always verify whether the user deployed the flow **after** the property value was changed.