There is no data when response_variable in scripts in mode: queued

[malinovsku]

The problem

When running the script in queued mode and stopping with response_variable, the variable is empty. At the same time, in other modes, the data is returned

What version of Home Assistant Core has the issue?

2023.11.2

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

script

Link to integration documentation on our website

https://www.home-assistant.io/integrations/script/

Diagnostics information

No response

Example YAML snippet

alias: test
sequence:
  - variables:
      resp:
        oth1: 12
        oth2: 99
  - stop: ""
    response_variable: resp
fields: {}
mode: queued

Anything in the logs that might be useful for us?

-

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (script) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of script can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign script Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

script documentation
script source
_{^{(message by IssueLinks)}}

[toxikman]

+1
Still seeing this is Core 2024.1.3.
The bug occurs even when the script is called once. More than one does not need to be queued. If this is an intentional missing feature then it should be in the documentation for Scripts (response_variable).

[PillarsZhang]

+1
I wasted a lot of time before realizing this was the issue.

[jleinenbach]

Same here. I think the response_variable could be any name and it's filled with all function return values.
So stop should fill all the variables into this response_variable with any name.
My response_variable is even filled with the string "Success" - it's not even a dict.

[JeffCrum1]

I am seeing the same thing using set_conversation_response in an automation when mode: queued is used. The response is fine when mode: single.

When mode: queued, I only get 'Done' with any command for the automation.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[toxikman]

Damn, how do I reopen this? This is a valid bug in the software!

[toxikman]

Please re-open this @frenck thank you.

[teskanoo]

home-assistant/home-assistant.io#34738

I have submitted a pull request to update the documentation to reflect the fact that response_variable is not honoured in queued mode scripts

[frenck]

As requested, as it seems to be still the case.

[dusker33]

I found that response_variable not work in conditions, too:

alias: test
sequence:

• if:
  • condition: template
    value_template: "{{ 1 == 1 }}"
    then:
  • variables:
    resp:
    mess: 1111
  • stop: ""
    response_variable: resp

Empty response

[mathmaniac43]

@dusker33 That relates to #125671