Skip to main content

Scheduled Jobs Block

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

This block shows the most recent successful and failed scheduled jobs. You can see information about what a scheduled job does, when it was last run, how frequently it runs and for how long. For failed jobs, you can also see the log incident number making it easier to find the issue in the log file when troubleshooting issues.

Note

If your school isn’t licensed for a particular J1 Web module, then the scheduled jobs for that specific module do not run. For example, there are several Advising module only scheduled jobs. If your school is not using the Advising feature, then those Advising related scheduled jobs do not run.

All schools run common and standard scheduled jobs.

  • To see a description of the scheduled job, the amount of time it took to run, and how frequently it runs, click the plus icon.

  • To get more information about a specific scheduled job error, access the Web Log File and search for the log incident number shown.

  • To see a full list of all successful and failed scheduled jobs, click View all scheduled jobs.

There are a few reasons you might not see a particular job:

  • The job hasn’t run yet

  • Only the most recently completed jobs are shown and the job you are looking for may have already run and no longer show in the block. To see a full list of scheduled jobs, click View all scheduled jobs.

  • Some scheduled jobs run automatically at startup and may have occurred before the ones shown. To see jobs that may have already complete, click View all scheduled jobs.

The total number represents the total ‘different’ individual jobs run for that day. A particular job that runs 20 times in one day only counts once.

A number that is automatically generated when a scheduled job error occurs. This incident number can help you locate additional information in the log file, which is used for troubleshooting issues. For more information, see the J1 Log File topic.