Recurring jobs usually maintain important business logic which helps you monitor service health, understand user behavior, make business decisions, etc., and you want to make sure to get the Recurring jobs' output on time for further analysis and dashboard reporting. If one of recurring jobs suddenly performs abnormally, failed or slow down a lot, it may impact your data processing pipeline and impact your business further.

In the lasted release of ADL Tools for Visual Studio, Related Job View was introduced to help you troubleshoot recurring job abnormal problems easily and quickly.

In Related Job View, you can find all related jobs for one job and get insights of the potential abnormal reasons:

1. The metrics graph at top shows the historical trend for recurring jobs with multiple metrics like duration, job input size, etc., and you can find the relationship between the trends to get the potential reasons for recurring job abnormal. For example, if you find the duration for one job suddenly increased a lot, at the same time the input data size also increased a lot, while other metrics didn't change much, then you'd better go back to check what's wrong with your input data.
2. The job list at bottom lists submitted recurring jobs, and you can compare the abnormal job with a normal one easily through right click. You usually need to pay attention to the big differences between these 2 jobs as they are probably the reasons causing job failure or performance issues.

More examples of how to troubleshoot recurring jobs can be found here: How to troubleshoot an abnormal recurring job.

Besides of scheduled recurring jobs, script submissions though VS from the same ".usql" file in U-SQL project are also tracked as related jobs. When developing a U-SQL script in Visual Studio, as a user, you usually need to submit the script to your ADLA account multiple times to verify the logic and result, as well as tuning the performance. Before, we don't have a good way to help you track these submissions coming from the same script, as a result, you need to open job browser and search the corresponding job name to find the jobs when you want to compare the current run with a particular pervious run. You can now right click the U-SQL script in project choose View Previous Run(s) to see all previews runs for the script in Related Job View.

Try this and contact us at [email protected] if you have problems and feedback.