xai-org/grok-build · error

{msg}

Error message

{msg}

What it means

In the remote restore flow, `RemoteRestoreOutcome::Failed(msg)` carries a failure message produced deeper in the restore pipeline (network, deserialization, or write failure while materializing the remote session). This site re-raises it verbatim via `anyhow::bail!("{msg}")`, so the actual text depends on the underlying restore step that failed.

Source

Thrown at crates/codegen/xai-grok-pager/src/app/session_startup.rs:1220

            } else if let Some(Err(e)) = restore_result {
                format!(
                    "Remote restore failed ({e:#}); continuing with conversation {local_session_id}."
                )
            } else {
                format!(
                    "Remote restore incomplete; continuing with conversation {local_session_id}."
                )
            };
            emit_pre_tui_restore_line(progress_on_stdout, &msg);
            Ok(ResolvedExisting {
                id: local_session_id,
                original_cwd: None,
                title: None,
                deferred_local_miss: false,
                suppress_code_restore: true,
            })
        }
        RemoteRestoreOutcome::Failed(msg) => anyhow::bail!("{msg}"),
    }
}
fn emit_pre_tui_restore_line(on_stdout: bool, line: &str) {
    use std::io::Write;
    if on_stdout {
        println!("{line}");
        let _ = std::io::stdout().flush();
    } else {
        eprintln!("{line}");
        let _ = std::io::stderr().flush();
    }
}
#[derive(Debug, Clone, PartialEq, Eq)]
pub(crate) enum RemoteRestoreOutcome {
    Restored { local_session_id: String },
    RecoveredAfterFailure { local_session_id: String },
    Failed(String),
}

View on GitHub (pinned to bc7f02eddd)

Solutions

1. Read the propagated `msg` in the error output to identify the underlying failure and fix that directly.
2. Check connectivity/auth to the remote session backend, then retry the resume.
3. Upgrade/downgrade the CLI so its snapshot format matches the one stored remotely.
4. Ensure the target worktree is writable (permissions, disk space) before resuming.

// Pre-check connectivity/auth to the remote backend before resuming
let healthy = remote_backend_health_check().unwrap_or(false);
if !healthy { eprintln!("Remote backend unreachable; fix network/auth before resume"); }

match grok_resume_remote(id) {
    Err(e) => {
        eprintln!("Remote restore failed: {e}");
        // surface the propagated `msg`, fix root cause, then retry once
        std::thread::sleep(Duration::from_secs(2));
        grok_resume_remote(id)?;
    }
    Ok(v) => Ok(v),
}

When it happens

Trigger: Calling the resume/startup path where `restore_session_from_remote(...)` (or a sibling step) returns `RemoteRestoreOutcome::Failed(msg)` — e.g. remote fetch error, snapshot parse failure, or failure writing the restored session files locally.

Common situations: Network outage or proxy blocking the remote backend during resume; remote snapshot format from an older CLI version; disk/permission errors when writing restored session state into the worktree.

Related errors

• send failed: {body}
• screen query failed: {body}
• resize failed: {body}
• wait failed: {body}
• stop failed: {body}

AI-assisted analysis of xai-org/grok-build@bc7f02eddd (2026-08-31). Data as JSON: /api/errors/2e30141c3a6807d6. Report an issue: GitHub.