warpdotdev/warp · error · anyhow::Error

Timed out refreshing team metadata

Error message

Timed out refreshing team metadata

What it means

Runner creation refreshes team/workspace metadata first so owner resolution can default to the team (refresh_workspace_metadata wraps the refresh in WORKSPACE_METADATA_REFRESH_TIMEOUT). If that refresh returns Err, the create aborts before resolve_owner runs.

Source

Thrown at app/src/ai/agent_sdk/runner.rs:107

    fn create(
        &self,
        output_format: OutputFormat,
        args: CreateRunnerArgs,
        ctx: &mut ModelContext<Self>,
    ) {
        // Mirror the server rule client-side so users get a fast, clear error.
        if let Err(msg) =
            validate_os_config(args.os, args.docker_image.as_deref(), args.macos_version)
        {
            super::report_fatal_error(anyhow!(msg), ctx);
            return;
        }

        // Refresh team metadata so owner resolution can default to the team.
        let refresh = super::common::refresh_workspace_metadata(ctx);
        ctx.spawn(refresh, move |_, result, ctx| {
            if result.is_err() {
                super::report_fatal_error(anyhow!("Timed out refreshing team metadata"), ctx);
                return;
            }

            let owner =
                match super::common::resolve_owner(args.scope.team, args.scope.personal, ctx) {
                    Ok(owner) => owner,
                    Err(e) => {
                        super::report_fatal_error(e, ctx);
                        return;
                    }
                };

            let factory = ServerApiProvider::as_ref(ctx).get_factory_client();
            let input = build_create_input(args, owner.into());

            ctx.spawn(
                async move {
                    let upserted = factory.upsert_runner(input).await?;

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Retry the create command
2. Verify network/proxy access to the warp-server URL
3. Confirm auth is healthy (`warp whoami`) so the refresh can authenticate
4. Check server health if failures cluster in time

for i in 1 2 3; do
  out=$(warp runner create $ARGS 2>&1) && { echo "$out"; exit 0; }
  case "$out" in *'Timed out refreshing team metadata'*) wait $((i * 5));; *) echo "$out" >&2; exit 1;; esac
done
echo 'team metadata refresh kept timing out' >&2; exit 1

When it happens

Trigger: `warp runner create` when the workspace/team metadata request to warp-server times out — slow or blocked network, server latency, or an expired auth token failing mid-flight.

Common situations: Flaky VPN or tethered connections; staging under load; first command after a long idle period re-authenticating slowly.

Understand the failure class

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

Related errors

• Timed out refreshing workspace metadata
• Timed out refreshing team metadata
• Failed to fetch images: {}
• Timed out waiting for Warp Drive to sync
• Failed to fetch images: {err}

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