Just wondering out of curiosity what happens when you hit "run now" to fire off a scheduled task.

It seems to take an excessively long time if all it is doing is inserting a row in a DB table.

Even on a fast server it's take 4 or 5 seconds.

Can anyone explain what DNN is doing here?

thanks

Gus

---

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com

Don't think I made myself clear.

When I hit "Run now" a rotating icon appears and there is a delay of at least 5 seconds and up to 15 seconds on my machine.
I don't care if the scheduled task doesn't run immediately.

Why does it take so long to finish adding a job to the queue and showing the message "item added to schedule for immediate execution".?

If all it is doing is adding a row to the DB then I could do that in SQL server in a split second.

It takes so long one would think it's recyling the app pool.

Gus

---

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com

Can you explain what is actually happening please? Do you mean the worker process? I can find not queue table.
What happens when a job is added to run.

Also, what changed after 8.0.3 to improve this?

thanks
Gus

---

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com