Errors
How CID surfaces failures, in the UI and inside a run.
Any action that fails in the app — saving a form, testing a connection, starting a run — shows a red notification in the bottom-right corner with the reason, rather than failing silently. Form fields that need fixing are highlighted in place.
Failures during a run are handled at two levels:
- A failure before any step even starts (missing server or SSH key, missing repository path, SFTP sync failure) is written into the Setup log, and the whole run is marked failed.
- A failure inside a specific step (its script exits non-zero, or a server connection drops mid-step) marks that step failed with an
exit Nbadge and its error in its own log, and every step after it is marked skipped — they never run. - A run you cancel is marked cancelled, not failed.
CID does not write a local error log file to disk. The run's own stored output (see Logs) is the durable record of what went wrong — there's no separate %APPDATA% error log the way some other desktop tools have.
Something missing or wrong here? Let us know
