#UX 101 Bug: Cancelling either does nothing or causes *further* delays (errors, etc)

1 messages · Page 1 of 1 (latest)

hushed hearth
#

If anything, cancelling makes it LONGER since you can't see the result (and need to still wait for the result to finish, for whatever reason, defeating the purpose of a cancel button) and you often get an error that requires refreshing the page. The average result is getting an error with the option to regenerate (when you may not even want to regenerate).

At the moment, the cancel button is a useless illusion - it does not do what is expected.

  1. You accidentally send the wrong message (eg: Create a resume instead of cover letter). You know this will be a long, long message.
  2. Cancel the prompt response.
  3. A pandora's box of bugs opens, either resulting in:
  • You cancelled the response. However, you can't type a new response until the original is actually done, rendering cancel pointless
  • You get an error in a box of vague, unhelpful messages that often require you refresh the page. "Message in conversation not found" is a common one.
  • There was an "error generating the response" with the only option to [REGENERATE]. We may not want to regenerate; we may simply want to move on. For example, the entire reason for cancelling may be we want to rephrase the prompt - but we have to regenerate and wait again to move on.

Frustration ensures - this is just basic UX; in this case, it's a bug since it doesn't do what it says.