$ loading▍
$ loading▍
Exact error messages you might see, and what to do about them.
this page on cid.pumpkins.dev| Message | What it means / fix |
|---|---|
| Set a local repository path for this project before running a workflow. | Go to the project's Settings tab and choose a local folder. See Add a repository. |
| The local path for this project is not a git repository. | Point it at a folder you've actually git cloned — CID never creates the clone for you. |
| The server configured for this workflow was not found. | The workflow's server was deleted. Edit the workflow and pick another server under Runs on, or This computer. |
| The server configured for this workflow has no SSH key. | Open Connections and attach an SSH key to that server. |
| ssh-keygen was not found on this system. Install the OpenSSH client, or import an existing key pair instead. | Install OpenSSH, or use Import existing instead of Generate new when adding an SSH key. |
| Unable to reach the server. Please try again. | CID-app couldn't reach the API — check your internet connection, or API_URL if you're self-hosting. |
| Git Bash is not installed. | The workflow uses Git Bash but Git for Windows isn't installed. Install it, or switch the workflow's shell to PowerShell or Command Prompt. |
| Only admins and the owner of this project can do this. | Your role on a shared project doesn't allow this. Ask the owner or an admin to change your role. |
| Viewers can't do this. Ask an admin of this project for the Member role. | Viewers can only read workflows, runs and logs. Running a workflow needs the Member role or higher. |
| This invite is for … Sign in with that email to accept it. | You're signed in with a different email than the invite was sent to. Sign out on the invite page and sign in, or create an account, with the invited email. |
| No files matched … | An artifact path didn't match anything after the run. Check the path in the workflow's Artifacts section — relative paths start from the project folder. |
-ErrorAction SilentlyContinue to commands that are allowed to fail.authorized_keys.Remember it's local-git polling, not a webhook — see Push trigger. Make sure new commits actually land in the local folder CID is watching on the machine running CID-app, and that the branch matches (or the branch field is blank).
On a shared project, each push and each scheduled time runs once, on whichever member's computer claimed it first. Check Started by on the project's Runs tab. See Teams & members.
CID-app has to be open on a machine that's signed in for its schedules to run — closing the app pauses them. Also check the workflow is Enabled (the switch at the top of the editor); disabled workflows show a Disabled badge in the list.
Sessions expire after 7 days — sign in again with the same email and password. If you were offline, CID keeps you signed in with cached account info until it can verify with the server again.