Restart Runtime

Last modified by Erik Bakker on 2023/01/24 16:08

In this microlearning, we will focus on the action to restart a runtime. In some cases, it can be beneficial to restart a runtime.

Should you have any questions, please contact  academy@emagiz.com.

1. Prerequisites

  • Basic knowledge of the eMagiz platform

2. Key concepts

This microlearning centers around restarting a runtime
With runtime, we mean: This is the component in which the individual integration flows are deployed into

  • By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
    • Flows return in original state

3. Restart runtime

In this microlearning, we will focus on the action to restart a runtime. In some cases, it can be beneficial to restart a runtime. Before we delve into how to let us first consider the effect and implications of our actions.

  • By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
    • Flows return in original state

As you can see this action does not alter the state of your runtime by being executed. To execute this action please navigate to Deploy -> Architecture (if you are not there already). After you have done so you can access the context menu of a particular runtime (via a right mouse click), while in "Start Editing" mode, and select the option called restart runtime.

novice-emagiz-cloud-management-restart-runtime--context-menu-runtime.png

After a grace period please execute the standard checks, i.e checking the logs under Manage -> Log Entries and verify if you can access the runtimes via runtime dashboard.

4. Key takeaways

  • By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
    • Flows return in original state

5. Suggested Additional Readings

There are no suggested additional readings on this topic