Operations and history
Operations
Section titled “Operations”Every change ProjectStart makes to a real resource (creating, editing, trashing, restoring or purging a project, changing its Git host, adding a repository) runs as an operation: an ordered list of steps, recorded before any of them starts.
- A project’s status badge opens its latest operation attempt, with each step’s state and a live console.
- A project’s Settings › History lists its operations, newest first, with a link to all of the project’s History.
- An operation that waits for another to finish says it is waiting, until its work starts.
- Operations for different projects run at the same time.
- Each operation is a History entry; Settings › History keeps every entry, with who did what, and exports them as CSV (see Review).
When something fails
Section titled “When something fails”- When a step fails, ProjectStart undoes the failed step first, then the completed steps in reverse order. Each undo checks what is really there before changing it, so nothing that isn’t this project’s is touched.
- After an interruption (ProjectStart restarted, for example), the operation carries on from where it was; a step is never assumed to have finished.
- The failed operation says what failed and what you can do next.
Retry first finishes any undo still pending, then starts a new attempt of the same operation.
When an undo couldn’t finish
Section titled “When an undo couldn’t finish”If undoing a failed step couldn’t finish, the project stays locked against conflicting work, and a refusal names Retry and Purge as what you can do. Purge stays available.
Success and cleanup
Section titled “Success and cleanup”Success is recorded before any cleanup. If a cleanup step then fails, the success stands: the cleanup is noted as pending and tried again later.