Does someone has also this problem when scheduling a new vulerability was scan with a time limit?
Here, 1 hour max to finish scan is scheduled:
When running, the scan constraints have been traduced to 25 hours time limit.
First of all, thanks a lot for raising this issue to our attention.
This is indeed an issue we have identified and fixed as part of our very next WAS module release.
The cancel time was wrongly computed as following: next run time + # of hours to cancel the scan. So I assume in your case this was a daily scan, hence the 25 hours...
Thanks Axel for your quick response.
I'm sure that I already saw this feature working (and also not working in fact sor some scans).
So it's a regression.
1) Is there a way Qualys could inform customers about this kind of problem that can affect their daily usage?
2) I've seen the problem on new schedules. What about already defined schedules (we've got some weekly ones)?
Yes this is a regression introduced the WAS module 3.6.0 version - all schedules will be impacted.
I definitely agree with your idea for informing customers about "known" issues - we have in fact this page already available for our TAMs so that they can be made aware of such impacting issues.
Let me discuss this within the team and with our Support team to see if we can come up with such solution.
Thanks. Please let me be informed.
It should be corrected now.
Retrieving data ...