windmill-labs/windmill · error
Could not find ${metaPath}. Does the folder exist locally?
Error message
Could not find ${metaPath}. Does the folder exist locally? What it means
Pre-flight check in the folder push command: stat() failed on f/{name}/folder.meta.yaml, so there is no local folder metadata to push. The push flow needs that file (it carries summary/extra perms for the folder); the input at fault is the folder name argument — no such local folder exists, or it was never created via newFolder/synced down so its meta file is missing.
Source
Thrown at cli/src/commands/folder/folder.ts:161
...localFolder,
},
});
} catch (e) {
//@ts-ignore
throw Error(`Failed to create folder ${name}: ${e.body ?? e.message}`);
}
}
}
async function push(opts: GlobalOptions, name: string) {
const workspace = await resolveWorkspace(opts);
await requireLogin(opts);
const metaPath = `f${SEP}${name}${SEP}folder.meta.yaml`;
try {
await stat(metaPath);
} catch {
throw new Error(`Could not find ${metaPath}. Does the folder exist locally?`);
}
console.log(colors.bold.yellow("Pushing folder..."));
await pushFolder(
workspace.workspaceId,
name,
undefined,
parseFromFile(metaPath)
);
console.log(colors.bold.underline.green("Folder pushed"));
}
async function addMissing(opts: GlobalOptions & { yes?: boolean }) {
const fDir = `f`;
try {
await stat(fDir);
} catch {View on GitHub (pinned to e474e8803c)
Solutions
- Run the command from the workspace root where f/ lives (the path is relative to cwd)
- Create the folder first: wmill folder new <name> (or wmill sync pull) to materialize folder.meta.yaml
- Check the folder name spelling — it must match the directory under f/ exactly
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at cli/src/commands/folder/folder.ts:161 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03).
Data as JSON: /api/errors/359be14669faa05f.
Report an issue: GitHub.