OpenFn / OpenFn/kit

Sync: You have to fetch a project before you can deploy it

Open
#1,303 1 comment 0 reactions 2 assignees View on GitHub

@doc-han is already working on this.

Since Mar 24, 2026.

CLI
Dominant language
TypeScript
Stars
21
Forks
23
Avg merge
1d 22h
Merged PRs (30d)
17

Description

When deploying a local project for the first time, you'll get an error like:

$  pnpm openfn project deploy fd2e0806-0099-47ad-93f6-c53d1464158e --endpoint --api-key

ERROR: Failed to find tracked remote project fd2e0806-0099-47ad-93f6-c53d1464158e locally
To deploy a new project, add --new to the command
You may need to fetch the project before you can safely deploy

[CLI] ✘ Command failed!
[CLI] ✘ Error: Failed to find remote project locally
    at handler (file:///home/joe/repo/openfn/kit/packages/cli/dist/process/runner.js:2462:11)
    at async parse (file:///home/joe/repo/openfn/kit/packages/cli/dist/process/runner.js:3985:12)

This can happen if you pull from instance A and try to deploy to instance B.

But it shouldn't matter if you don't have that project locally - we should just fetch it down first.

I think this is an easy fix - I just want to think through any cases where it might be a problem. Or is that error just straight up wrong?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.