Travis, looking at my tasklist, I just found 2 Wus reported on the 13th which aren't insta-purged...

Click

BTW: those are still there... ;)

1641784
1635911

blarg. ok

Whatever "blarg" is - it didn't help. ;))

---

mic.

Well, it's been weeks since there seems to have been any DB issues here, so can we go back to a 12 hour purge delay?

One thing this would do is it would allow me to release my hosts from a restricted network access regimen (so I have time to log the data for my hosts without missing datapoints) and thus they would be sending their completed tasks back sooner.

The way it stands, I figured out how much cache I have to carry with the other projects I run to cover a 24 hour period. Then I pound on you until I get that much work onboard, and then have them clam up until the next day to report and repeat the cycle.

Ordinarily when you had at least a 12 hour purge delay, I would run with minimum cache settings and let them talk to the project anytime they wanted. This meant I could get my tasks back to you as quickly as possible while at the same time not miss any datapoints for my hosts.

Alinator

Travis, looking at my tasklist, I just found 2 Wus reported on the 13th which aren't insta-purged...

Click

BTW: those are still there... ;)

1641784
1635911

Been there quite a while, now ..

Is it possible to extend the time yet? 24 hours would be nice, seeing that most see only a few wu's/day anyways if that.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.