11

The admin page in the latest Sitecore version has what you are looking for. Go to /sitecore/admin for the admin overview or directly to /sitecore/admin/Jobs.aspx It will display like this: Not sure if it does exactly the same as Rocks but it's a start.


7

They don't persist, nor can they (out of the box) As you've already mentioned, they do not persist across application pool resets. You're not doing anything wrong, they just aren't designed to persist. They live in the memory of whatever server triggered them. So as far as "traditional Sitecore" goes, be it Scheduled Tasks, Jobs or Agents - you are ...


4

Finally figured out how to do this. Firstly, you want to make sure you start the Refresh/Rebuild properly. What I mean by that is that if you want to be able to identify the right crawler related to a given Indexing Job, you will need to tag the Indexing Job with some ID. You can do that by adding a Message to the job when starting it. Job myRefreshJob =...


3

You're right. There is a database agent configured in Sitecore configuration, e.g. for master database: <agent name="Master_Database_Agent" type="Sitecore.Tasks.DatabaseAgent" method="Run" interval="00:10:00"> <param desc="database">master</param> <param desc="schedule root">/sitecore/system/tasks/schedules</param> <...


3

Yes, this is correct, Sitecore Jobs and Scheduled Tasks run as background threads, and any App Pool restart or unexpected shutdown of the server will cause the job to be killed. If you have a long-running job then you must defensively code for this possible outcome, and allow the code to both gracefully fail and pick up where it left off the next time the ...


2

Scheduler - Skypping inactive agent is generated by Sitecore.Task.Scheduler.ReadAgents class private static Scheduler.Agent[] ReadAgents() { Log.Info("Scheduler - Adding agents", typeof(Scheduler)); try { ArrayList arrayList = new ArrayList(); XmlNodeList configNodes = Factory.GetConfigNodes("scheduling/agent"); ...


2

The JobRunner processors in the Job pipeline are responsible to manage the execution of queued jobs, like indexing jobs. You can control their execution frequency modifying the value of the Jobs.QueueProcessingInterval setting, set to 2 seconds by default: <!-- JOB QUEUE INTERVAL Gets the interval between the JobManager checking its queue for ...


1

Could you please try to execute your scheduler with PowerShell Script Options? It provides you an option to execute the scheduler with a single click, the purpose to suggest this solution is when you click on the Run Scheduler Task option from the Script Menu, it will execute your scheduler without any delay. You can verify that scheduler executes or not. ...


Only top voted, non community-wiki answers of a minimum length are eligible