warpdotdev/warp · error
Saved prompt with ID '{id}' not found
Error message
Saved prompt with ID '{id}' not found What it means
The ID parsed to a valid SyncId, but CloudModel::get_workflow returned None (app/src/ai/agent_sdk/ambient.rs:297-304): no synced object with that ID exists in the local CloudModel. Typically a typo, a deleted prompt, or a prompt whose workflow has not yet synced to this client.
Source
Thrown at app/src/ai/agent_sdk/ambient.rs:301
};
let cloud_model = CloudModel::handle(ctx);
let workflow = cloud_model.as_ref(ctx).get_workflow(&sync_id);
match workflow {
Some(cloud_workflow) => match cloud_workflow.model().data.prompt() {
Some(prompt_text) => Some(prompt_text.to_string()),
None => {
super::report_fatal_error(
anyhow::anyhow!("'{id}' is not a saved prompt"),
ctx,
);
return;
}
},
None => {
super::report_fatal_error(
anyhow::anyhow!("Saved prompt with ID '{id}' not found"),
ctx,
);
return;
}
}
}
None => None,
};
let loaded_file = match args.config_file.file.as_deref() {
Some(path) => match super::config_file::load_config_file(path) {
Ok(file) => Some(file),
Err(err) => {
super::report_fatal_error(err, ctx);
return;
}
},
None => None,View on GitHub (pinned to e72fd7aacb)
Solutions
- Re-run after ensuring Warp Drive sync completes (the command refreshes drive metadata as part of setup — retry once)
- Re-copy the ID from the current saved-prompts listing
- Confirm the prompt still exists and belongs to the authenticated account
Defensive patterns
Strategy: validation
Validate before calling
let sync_id: SyncId = ServerId::try_from(id.as_str())?.into();
let cloud_model = CloudModel::handle(ctx);
if cloud_model.as_ref(ctx).get_workflow(&sync_id).is_none() {
// refresh drive sync and re-check before invoking the run command
} Prevention
- After creating a prompt, wait for Drive sync to deliver its workflow before referencing it
- Re-verify IDs against the current prompts listing in long-lived scripts
When it happens
Trigger: Referencing a recently created saved prompt before its workflow syncs down via the Drive refresh; a deleted prompt; an ID from another account/workspace.
Common situations: Create-then-immediately-run flows losing the race with sync; IDs copied from a different environment; drive sync lagging or disabled.
Related errors
- Failed to parse saved prompt ID '{id}': {err}
- '{id}' is not a saved prompt
- API key '{key_identifier}' not found
- Runner '{id}' not found
- Runner '{name}' not found
AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16).
Data as JSON: /api/errors/22d30c7d57794f82.
Report an issue: GitHub.