stonezdj(Daojun Zhang)

You also could query in the security Hub to find out the image with critical CVE's

The original commit related to this line means to reduce the priority of this queue to reduce the impact of the slack, the slack might be rate-limited sometimes. it is...

Yes, the jobservice dashboard can't answer this issue, the scan all UI should display some useful information for errors.

Could you please describe your integration scenario so that we could reproduce this issue?

In the current situation, the job can't complete in 1 hour, we should adjust the default execution sweep schedule from every hour to every day or editable setting

Another question: Has ever this Harbor instance been upgraded from a version older than v2.3.0? see the faq: https://github.com/goharbor/harbor/wiki/Harbor-FAQs#duplicate-repository-name-in-the-same-project

Can you please try to reproduce the issue in the latest harbor? for example: https://demo.goharbor.io

It seems that you created this rule through API and the `algorithm` field is missed. default it should be `"algorithm":"or"` the backend API should validate the input first or use...

The jobservice log location: /var/log/harbor/jobservice.log

With the pr #20358 merged, it could display the log and status is Error