Repository navigation
Kitewell 0.26.1 — Public beta
Pre-release
Pre-release
Kitewell 0.26.1 is a beta update.
What's in this release
- The chat says what waits for you, such as "A step waits for your reply"
or "2 changes to decide". Clicking it lists each one with what it asks
and since when, to open or to set aside as no longer needed. The chat,
Home, the project list, and the menu bar count the same things, and
Runs → Waiting lists every wait, however old. - A project runs where it was made. A computer shows and runs the projects
made on computers, its own and its team's, which Projects from your
team brings over. Projects made in Kitewell Cloud stay there. - This computer's connection and plan read the same everywhere. When
Kitewell Cloud no longer accepts the computer, one message says so and
until when everything keeps running, and Sign in again opens the
browser at once. A plan granted by contract shows as licensed, with no
purchase buttons. - Runs are named by their workflow and start time, with Copy run ID in
the run's menu. A run that waited for approval keeps what started it,
and a sheet's runs name their sheet and row. - Schedules read as sentences, such as "On day 1 of every month at 07:00".
- The chat shows what each step did in plain words, with the raw details
folded away, and finished steps say what they did. Thread titles and
replies follow the language you write in. - A paused project explains itself on every page, and Run now offers
to resume it first. - Japanese reads as Japanese throughout: 2分45秒, lists joined with 、,
パソコン, and 対応待ち apart from 待機中. - Errors on the Connect AI apps page and in syncing say what happened and
what to do, in your language. - Pages open faster: the workflow and knowledge editors load when first
opened. - After an update, projects read "Finishing the update…" while Kitewell
moves them onto the engine the new version brings. That move and backups
no longer wait for runs that wait on a person.
Upgrading
Nothing to do. Kitewell 0.26.0 updates itself to 0.26.1 at a quiet moment,
and running workflows go on across the restart.