Every upload, profile picture and custom emoji now gets an answer in time, even when our file storage provider stalls. If storage is still working 85 seconds after a request reaches Kemble, Kemble answers that storage is busy and says how long to wait, and the app sends that part again by itself, waiting as long as asked, up to 30 seconds at a time. If the network in front of Kemble gives up on a file sent in one request, the app now says plainly that the file may still have arrived, so you can check before sending it again, instead of showing a connection error. Workspace and personal data exports are no longer started a second time when storing them is slow, and text previews and a file’s details no longer wait on a slow storage before showing what they can.
If you sign in with Google or a phone number in a tab opened before an update, Kemble now says it was updated and offers a Reload button, instead of saying sign-in failed. A text box you are typing in on a whiteboard no longer closes when Kemble checks for an update, and unsaved changes on a canvas or whiteboard, including edits made offline, keep Kemble from reloading by itself; it tells you why. The emoji picker and animated emoji try again after a dropped connection instead of giving up until you reload. When Kemble’s live connection restarts during an update, everyone’s “last seen” time is still recorded.
When Kemble hasn’t loaded someone’s name yet, it no longer calls them “Former member”. You see a short placeholder, or a count such as “Ada and 1 more are in it”, until the name arrives. This covers a private thread’s “Added by”, profile fields, bulk moderation, a Link’s people and activities. “Former member” now appears only when the account really is gone, and in lower case inside a sentence (“Added by a former member”).
On kemble.io, the Sign in and Open Kemble links now go straight to Kemble without a redirect, and still open Kemble Work or Kemble Circle from that product’s own page. For developers, the Files and large uploads page says that a request whose storage is still busy answers 503 storage.busy within 85 seconds, and gives every size exactly: Kemble’s own limits in MiB, and the 100 MB a single request may carry in Cloudflare’s own unit.