All demos

A repository that does not start keeps its canvas running

Shared by Daniel Sadilek on October 21, 2026

When a saved configuration changes how a repository's agents work and the new set-up cannot start (say, a clone cannot be made because the remote does not answer), the agents now carry on as they were set up before instead of stopping. The configuration shows the problem at that repository, with the reason and a Try again button, and the count on the Configuration button keeps it visible on every canvas. A canvas that cannot start after a restart is no longer silently missing: the page says why and offers Try again.