Skip to content

Say what came of an approved action when its conversation could not be carried on - #1592

Open
davidmckayv wants to merge 2 commits into
mainfrom
approval-left
Open

davidmckayv wants to merge 2 commits into
mainfrom
approval-left

Conversation

@davidmckayv

Copy link
Copy Markdown
Contributor

What this changes

A step whose conversation could not be carried on after the person decided it now says what came of it.

Found in testing. A person allowed a Slack post, the post went out, and the conversation could not be carried on afterwards. The step said "Send message…" for good, with nothing to say the post was made. The next message then told the Bot "no result came back" for a call that had run, which invites it to post again.

  • A request in the approvals inbox can carry left: whether the action was done, the sentence that says so, and the answer the conversation never received.
  • The step draws that sentence under itself, and beside a folded group of steps ("Used Slack") where a waiting card would be: "Done: send message on Slack. OpenBot couldn't carry on the conversation after that, so nothing else was done. Send a message to continue."
  • The next message sends the Bot the kept answer for that call in place of "no result came back" (leftAnswers, repairUnansweredToolCalls).

Evidence

Tests (app/tests/approval-left-not-carried-on.test.tsx): the sentence under a step, beside a folded group, as an alert when the action was not done, and the next message's history carrying the kept answer. All four fail on main.

Real product, Chromium and WebKit headless, light and dark, with the thread lock refused after the person allowed a Slack post: the post was made once, the step said "Done: send message on Slack. …" about 50 seconds later, and after recovery the Bot answered "Yes, 'the deck is ready' was posted in #launch." without posting again.

…e carried on

An allowed Slack post went out, the conversation could not be carried on after it, and its
step said "Send message…" for good with nothing to say the post was made. The step now
draws the outcome its request holds: whether the action was done, that nothing followed it,
and to send a message to continue. The next message sends the Bot the answer the
conversation never received in place of "no result came back", so it does not post again.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant