warpdotdev/warp · error · anyhow::Error

Timed out refreshing team metadata

Error message

Timed out refreshing team metadata

What it means

Thrown when refreshing workspace/team metadata via TeamUpdateManager::handle(ctx).update(...) does not complete within WORKSPACE_METADATA_REFRESH_TIMEOUT (10 seconds, app/src/ai/agent_sdk/common.rs:30). The with_timeout wrapper converts the elapsed future into an Err, which is mapped to this anyhow message. It signals that the server round-trip for team metadata (members, settings) stalled, not that the data is invalid.

Source

Thrown at app/src/ai/agent_sdk/common.rs:151

///
/// This ensures that team state is up-to-date before creating cloud objects or performing
/// other operations that depend on team membership.
pub fn refresh_workspace_metadata<C>(
    ctx: &mut C,
) -> impl Future<Output = anyhow::Result<()>> + Send + 'static + use<C>
where
    C: GetSingletonModelHandle + UpdateModel,
{
    let refresh_future = TeamUpdateManager::handle(ctx).update(ctx, |manager, ctx| {
        manager
            .refresh_workspace_metadata(ctx)
            .with_timeout(WORKSPACE_METADATA_REFRESH_TIMEOUT)
    });

    async move {
        let _ = refresh_future
            .await
            .map_err(|_| anyhow::anyhow!("Timed out refreshing team metadata"))?;
        Ok(())
    }
}

/// Refresh Warp Drive before executing an operation.
pub fn refresh_warp_drive(
    ctx: &AppContext,
) -> impl Future<Output = anyhow::Result<()>> + Send + 'static + use<> {
    UpdateManager::as_ref(ctx)
        .initial_load_complete()
        .with_timeout(WARP_DRIVE_SYNC_TIMEOUT)
        .map_err(|_| anyhow::anyhow!("Timed out waiting for Warp Drive to sync"))
}

/// Fetch the conversation's server metadata and validate that its harness matches the caller's
/// `--harness` choice. Returns the metadata on success so the caller can reuse it (e.g. for the
/// server conversation token).
///

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Check network connectivity to the Warp server endpoint and retry the command — the timeout is a fixed 10s so transient slowness is the most common cause.
2. Re-authenticate (warp logout / warp login) if requests are silently looping on an expired token.
3. If it reproduces consistently on a fast network, capture logs for the TeamUpdateManager update and report a possible deadlock/stall in refresh_workspace_metadata.
4. As a maintainer, consider retrying once with backoff or surfacing the underlying future's state instead of only the timeout.

Example fix

// before
let _ = refresh_future
    .await
    .map_err(|_| anyhow::anyhow!("Timed out refreshing team metadata"))?;

// after (retry once before giving up)
let result = refresh_future
    .await
    .map_err(|_| anyhow::anyhow!("Timed out refreshing team metadata"));
if result.is_err() {
    log::warn!("team metadata refresh timed out; retrying once");
    // rebuild the update future and await it again before failing
}

let start = std::time::Instant::now();
if !net_up() {
    anyhow::bail!("no network; team metadata refresh will time out");
}
fn net_up() -> bool {
    std::net::TcpStream::connect("stable.warp.dev:443").is_ok()
}

match refresh_team_metadata(ctx).await {
    Ok(()) => {},
    Err(err) if err.to_string().contains("Timed out refreshing team metadata") => {
        log::warn!("team metadata refresh timed out; continuing with cached metadata");
        // or retry once with backoff before surfacing
    }
    Err(err) => return Err(err),
}

When it happens

Trigger: Calling the agent-SDK helper that wraps refresh_workspace_metadata(ctx) with .with_timeout(WORKSPACE_METADATA_REFRESH_TIMEOUT) — i.e. any ambient-agent operation that first refreshes team metadata. It fires when that future does not resolve within 10s: slow/blocked network, server latency, expired auth token forcing retries, or the TeamUpdateManager model being busy/deadlocked.

Common situations: Running warp CLI agent commands on a flaky connection, VPN half-open tunnels, CI runners with no network egress, clock-skewed auth, or a saturated event loop where the manager update never gets scheduled. Also seen right after login when a first metadata fetch races a token refresh.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

Related errors

• Timed out waiting for Warp Drive to sync
• Timed out waiting for Warp Drive to sync
• Failed to fetch images: {}
• Failed to fetch images: {err}
• Error polling OAuth status: {err}

AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16). Data as JSON: /api/errors/cf9d81be484c6fe8. Report an issue: GitHub.