A compliance check is failing. Before changing a policy or uploading another document, open the result and establish what the check actually observed.
This walkthrough uses the Sythe platform to move from a failed result to the evidence and the next evaluation. You need access to Tests in the correct organization. Some actions depend on your permissions and the check's eligibility.
Open the result that needs attention
From Tests, open the check. In Results, read the status, affected resources, and How to remediate guidance. Check Last evaluated before treating the result as a statement about the present moment.
If the detail shows Source observed or Result valid until, read those alongside the evaluation time. A recently displayed result and recently collected source data are different things. Where the page lists an owner or deadline, use that context when deciding who needs to act.
For a walkthrough, choose a known issue in a demo organization. Do not manufacture a failure by weakening a customer's security setting.
Inspect what supports the result
Open Evidence. Review the supporting material and any Evidence review or Policy source approval information shown for this check. A generated document or collected record does not, on its own, establish that a person approved it.
Open Controls and Frameworks to see what the check supports. Those relationships help you understand why the issue matters. They do not turn one result into a verdict on an entire audit.
Suppose a record is missing an approval. The useful next step is to resolve that approval through the applicable workflow, not to keep rerunning collection until the status changes. If the source is outdated or inaccessible, investigate that condition before assuming the underlying control failed in practice.
Fix the underlying issue before running again
Complete the remediation in the system or workflow that owns it. Then return to the check and use Run again when the action is enabled.
If the button is unavailable, read its explanation. Repeated clicks or a different browser will not supply a missing permission or satisfy an eligibility condition. Keep the reason with your follow-up work so the next person knows what is blocking evaluation.
The rerun starts another evaluation. It does not authorize the platform to make every required business decision for you.
Read the new run in History
Open History and inspect the resulting evaluation. Compare its status, headline, and timestamp with the earlier failure. Return to Results to inspect the current affected resources. If the result is unchanged, return to the evidence and check whether the intended change reached the observed source.
A history-loading error is also different from having no previous runs. Resolve the loading problem before using the absence of rows as evidence.
Before closing the issue, identify which run demonstrates the result you are accepting. That gives the next reviewer a concrete record to inspect instead of a message saying someone clicked the rerun button.