Executing a Job

Once the job is created, we can run it either manually or by scheduling it. In this article, we will cover the step-by-step guide for running the job manually. For scheduling a job, you can refer to this article. The following topics are covered in this article:

• Updating the existing job
• Executing the job manually in Development Workflow.
• Reviewing the 'Activity' screen of an app. 
• Understanding the execution of the steps.
• Previewing the output after running the job.

In the previous article 'Creating a job', we created an app named 'Demo Job' as shown in the screenshot below.

Let's go through the steps to run the job 'Demo Job' manually:

1. Click 'Demo Job' shown in the above screenshot. 
2. Once you select 'Demo Job', the 'Update Job' window will open as shown below:
   
   
   
   
3. Before running the job, you can adjust the configuration, if required. You have three options:
   • Save: This option will save the new configuration for future use.
   • Save + Execute: It will save the new configuration and immediately execute the job
   • Execute: This option will execute the job using the already saved configuration.
4.  In this example, we've set a custom date and utilized only one process in a step.
5. Click on 'Execute'.
6. Upon clicking 'Execute', the 'Update Job' pop-up will close, and the job will start executing.
7. Click the 'Activity' icon shown on the left sidebar. Upon clicking 'Execute', you will see an 'Activity' screen as shown below. This screen shows the list of jobs that were executed or being executed. In the below example, it shows the job that we just triggered. As it is our first job, it is suffixed by '-1' and for the next job, it will be suffixed by '-2'. 
   
   
   
   
8. Once you expand the job, you'll see the screen as shown below. The expanded view of the job displays all details, executed steps, activity logs, and an option to abort the job. Let's clarify the meaning of the icons associated with each job and process.
   •  Spinning Icon (): This icon represents the currently running job or the step.
   • Pending icon(): This icon represents the pending step or process.
   • Completed icon (): This icon represents that the job or the step has been completed successfully.
   • Aborted icon (): This icon represents that the job or step was aborted before completion. 
   • Failed icon (): This icon represents that the job step failed and hence, the job failed. 
     
     
     
     
9. We can expand each step to see its details. Generally, you will see 'Inframanager_create_cluster' as a first step when the cluster is not running. It creates the cluster and allocates the resources according to the runtime template selected. As the last step, you can see 'inframanager_terminate_cluster' if the runtime template has been configured to terminate after each job execution.
   
   
   
   
10. When the same job is run multiple times, only the latest job execution is shown under the 'Latest' tab. For example, in the screenshot below, the job by the name 'Demo Job' was run thrice. The 'Latest' filter shows only the last job i.e. Third Job.
    
    
    
    To see all executions, click on the 'All' tab and you will see all three execution details. Check below:
    
    
    
    
11. To verify the processed data, you can click on the dataset and preview the data. In the below screenshot, check that the 'Modified Date' is updated along with the total row count. To learn more about the output of processed data, please refer to the article 'App-Output'.