Troubleshooting Sync
“not inside a sync repository: .iflowkit directory not found”
You are not running the command from a sync repository.
Fix:
cd {packageId}
iflowkit sync pullThe repository root must contain .iflowkit/.
“missing metadata file: expected .../.iflowkit/package.json”
The directory has .iflowkit/, but the package metadata file is missing.
If it was deleted accidentally:
git checkout -- .iflowkit/package.json“{ENV} tenant not found for profile ...”
The required tenant service key was not imported for the resolved profile.
Fix:
iflowkit tenant import --env dev --file ./service-key-dev.json
iflowkit tenant import --env qas --file ./service-key-qas.json
iflowkit tenant import --env prd --file ./service-key-prd.jsonDEV is always required. QAS is required only for 3-tenant workflows.
PRD operation fails because confirmation is required
PRD requires explicit confirmation through --to prd.
iflowkit sync push --to prd
iflowkit sync pull --to prd
iflowkit sync deliver --to prdsync pull reports branch divergence
Your local branch and remote branch contain different commits.
Options:
- Rebase or merge if you want to keep local changes.
- Reset to remote if remote is the source of truth.
Example with caution:
git fetch origin
git checkout dev
git reset --hard origin/devsync deliver fails because working tree is not clean
deliver performs merge and deployment operations, so it requires a clean working tree.
git status
git stash push -u
iflowkit sync deliver --to qassync pull created a stash
sync pull may stash local changes before replacing IntegrationPackage/ with CPI export content.
Inspect stashes:
git stash listRestore if needed:
git stash popCPI upload or deploy failed and transport is pending
Fix the underlying problem first: authentication, network availability, CPI lock, endpoint issue or temporary server error.
Then rerun the same operation:
iflowkit sync push
iflowkit sync deliver --to prdThe CLI should continue from uploadRemaining, deleteRemaining or deployRemaining.
sync compare says target branch does not exist
Fetch remote branches and verify that origin/qas or origin/prd exists.
git fetch origin
git branch -rIf the branch is expected to be created by workflow, run the appropriate initialization or delivery flow.
Git is not found
Install Git and confirm it is on PATH:
git --versionShow deploy status
iflowkit sync deploy status --env dev
iflowkit sync deploy status --env prd --transport {transportId}