Troubleshoot RenderLog checks and visual results

Open the run detail and identify whether the failure came from navigation, a flow step, an assertion, output creation or baseline comparison. Confirm the URL, viewport, format and expected value. An empty expected text or value means the element or field must exist; it is not an invalid assertion.

For an unexpected visual result, verify that the run used the intended case, viewport and approved baseline. Rerun with force-fresh if cached input could hide a page change. Interrupted run batches recover from their recorded state, so do not create duplicate batches immediately. If the result remains wrong, share the run ID and expected outcome with support, not site credentials or private tokens.