There are two ways to run an audit: Ad-hoc and via the Scheduler…
Use this for one-off audits. For example, testing a setup configuration, or you just need a snapshot of the data quality right now.
Remember that not all spidered URLs are tested – that would be wasteful. Instead a random sample is taken (sample size optimised by the system). Hence you will see a number of options to choose from if an audit has already completed. Note, a new spider will always start if the previous is older than 30 days:
Use this when your setup is finalised and you wish to monitor data quality over time. The options you see here depend on the license you have purchased. Typically Monthly is sufficient as you will use the Current Status to check governance issues in near real-time. If you are undergoing major revisions to your website, use a higher audit frequency until the dust settles.
When an audit is running the notification bell turns red. Click on this to see what is happening.
When an audit is completed its status is removed from this section. In addition, if you have Edit or Admin access to this project, you will received an email notification when:
A project audit can only run if there is no existing audit currently running for the same project. You can always cancel a running project in the Report Log of the same page. It can take a few seconds for all the job queues to be stopped and the status to be refreshed.