Noted in Navigating Runtimes, the In Use column indicates whether or not the runtime template is used in an app job or a notebook. Clicking the Yes or No in this column navigates to the runtime template's Dependencies page.
The Dependencies page can also be navigated via the dependencies icon () from within the details of a runtime template. The runtime template Dependencies page displays all the apps and/or notebooks it is being used. Of course, if the In Use value is No then no data will appear in the list of dependencies.
Reviewing runtime template dependencies
The page displays a variety of information, some fields are only available based on the value of a dependent field. The below describes the various fields and explains when each is applicable:
- Type - App or Notebook, defines the type of object the runtime template is being used.
- Name - Name of the app or notebook the runtime template is being used. Clicking on the name takes the user to the detailed object.
The remaining fields are only applicable to those rows whose object type is an app:
- Job Name - The name of the job within the app that is utilizing the runtime template. Clicking on the name of the job takes the user to the activity logs section within the operations screen of the app.
- Job Step Name - The specific job process/step utilizing the said runtime template. The runtime template is set at each process/step of a job. Therefore, a single job may use, in theory, a different runtime template for each process/step.
- Environment - The value of Development or Production indicates the environment of the job utilizing the said runtime template.
- Scheduled - Indicates whether the job noted is scheduled. Scheduled jobs are only available within the production environment of an app.
- App Deleted At - This is blank for active apps but displays the date if an app has been deleted. This is significant if trying to delete a runtime template because a deleted app is still "using" the runtime template since the app can be restored from the trash.