Delete a user from the admin console without a server error
User deletion, chat exports, debug views and project pages in the admin console now finish their work and tell you what happened instead of returning a 500.
Running an admin task against a busy account used to end in a server error page or a truncated download, with no way to tell what actually happened. Several of those dead ends are gone.
User deletion that completes
Deleting someone who had threads on their own chats, or who had shared a restricted chat, failed outright and removed nothing. The delete now clears those rows and hands their restricted shares to the system user, so it completes and the shares other people rely on keep working. Anyone who has ever held a subscription or an invoice still cannot be deleted.
The delete also refuses to run when other members still hold access in the same tenant, so you cannot empty an organization that other people are working in.
Forked chat exports with debug and context
Exporting a forked chat produced an archive with the debug and context JSON missing, and a chat made entirely of forked messages answered "failed to export any messages". The export now reads each forked message's files from the message it was forked from, so the archive holds the UI, debug and context JSON you expected. If an export runs out of time, the archive includes an INCOMPLETE note saying how far it got instead of looking whole.
Debug view for a message whose original is gone
Opening the Debug view on a forked message whose original had been deleted returned a server error and showed you nothing. You now get the message's own debug data, or a plain "not available" when there is none.
Project pages that say not found
Pasting a project ID with no matching project returned a server error on the chats list, sessions list, indexing tab, reindex button and chat messages page, which read like the console was broken. All fourteen project pages now answer with a not-found response, pointing you at the ID rather than the service.
Exports and searches that answer
Deleting a user, exporting a chat, exporting the user CSV, searching and pulling a diagnostics log against a heavyweight target used to outlive the connection: the download cut off mid-stream and you saw no error. Each of those now finishes inside the time the console has to answer, so you get a response either way.
The next time you run one of these against a large account, you should see a result page or a complete download rather than an error you have to interpret.