karatelabs/karate · info

retry succeeded after

Error message

retry succeeded after {} attempt(s): {}

What it means

WARN log emitted when a retried condition finally evaluated true on the given attempt after the first check failed. It confirms the retry loop worked and the operation completed — it is informational, not an error, though it signals the condition was initially flaky.

Solutions

1. No action needed if the test passes — this is expected behavior for slow-but-successful waits.
2. If attempts are consistently 2-3+, add an explicit wait or delay before the action to reduce flakiness noise.
3. Consider increasing retry interval so fewer iterations are needed.

When it happens

Trigger: The Supplier<Boolean> condition passed to CdpDriver's retry helper returned false on the first check but true on attempt N (1..maxAttempts) after an interval sleep.

Common situations: Element appears a few hundred ms after an action; navigation completes just after the first poll; Chrome DevTools state settles slowly under load; CI machines with slow rendering.

Understand the failure class

Background: Request timed out: what client-side request timeouts mean across libraries (Request timed out, TIMED_OUT, APITimeoutError) — this error's family across 39 libraries.

Related errors

• retry started: (max attempts, ms interval)
• retry attempt / failed for
• no frame at index: after retries
• Page.navigate timed out, retrying
• Page.navigate returned ERR_ABORTED, retrying

AI-assisted analysis of karatelabs/karate@a22eb90246 (2026-09-12). Data as JSON: /api/errors/d82ba19a87122be8. Report an issue: GitHub.

Appendix: source

Thrown at karate-core/src/main/java/io/karatelabs/driver/cdp/CdpDriver.java:4283

        if (Boolean.TRUE.equals(condition.get())) {
            return true;
        }

        // Log that we're starting retries (helps diagnose flaky tests)
        logger.warn("retry started: {} (max {} attempts, {}ms interval)", description, maxAttempts, interval);

        // Retry loop
        for (int attempt = 1; attempt <= maxAttempts; attempt++) {
            // Abort on interruption instead of degrading into a busy spin: sleep()
            // preserves the interrupt flag, so every later sleep would return
            // instantly and the remaining attempts would hammer CDP back-to-back.
            if (Thread.currentThread().isInterrupted()) {
                logger.warn("retry aborted (thread interrupted): {}", description);
                return false;
            }
            sleep(interval);
            if (Boolean.TRUE.equals(condition.get())) {
                logger.warn("retry succeeded after {} attempt(s): {}", attempt, description);
                return true;
            }
            logger.warn("retry attempt {}/{} failed for: {}", attempt, maxAttempts, description);
        }

        // Log failure with driver state for diagnostics
        logger.warn("retry FAILED after {} attempts: {} | {}", maxAttempts, description, getDriverState());
        return false;
    }

    /**
     * Centralized retry mechanism using default options.
     */
    private boolean retry(String description, Supplier<Boolean> condition) {
        return retry(description, condition, options.getRetryCount(), options.getRetryInterval());
    }

    /**

View on GitHub (pinned to a22eb90246)