How-to guides

Re-ask an answer whose sources changed, in a branch

When a chat answer is labelled May be out of date, Re-ask in a branch asks the same question again against today's documents and opens Compare on the two answers. The original stays exactly as it was.

When a document a chat answer quoted changes, the answer is labelled May be out of date. You can get a fresh answer without losing the old one.

Steps

  1. Click the May be out of date label on the reply, or the label next to the conversation under What it has affected on the Knowledge page.
  2. Read what changed. The detail shows the version the answer quoted, the version that applies now, and, when you can open both, the two passages side by side.
  3. Click Re-ask in a branch.

GPTree makes a new branch where your question was asked, asks the same question again, and opens Compare with the Original answer on one side and the New answer, from today's documents on the other. Open the new branch takes you to it so you can carry on from there.

What it does and does not do

  • The original is never changed. The old answer stays where it was, label and all, so you can always see what was said and why.
  • It is one message. The new answer is charged like any message you send. Creating the branch costs nothing.
  • It uses the existing branch. The new branch appears in your conversation tree like any other, and your plan's branch limit applies as usual.
  • Chat only. Knowledge API answers are asked again through the API. Crew runs are not re-asked from here.
  • Nothing happens on its own. GPTree never re-asks for you; you choose when.

If a re-ask does not go through, the original answer is unchanged and you can try again.

Related reading