Response Variable doesn't work with Queued Mode

wstrater · February 20, 2025, 2:42pm

I created a script that uses a stop with a response_variable.

When I run the script using Actions in Developer Tools with the mode set to parallel, I get the value of the response_variable.

When I change the mode to queued, I don’t get the value of the response_variable.

I understand the complexity of coordinating the caller with an asynchronously queued execution so I am not surprised. The issue is I didn’t find this in the documentation when I looked at Script Modes or Stopping a Script Sequence.

Wes.

123 · February 20, 2025, 3:24pm

github.com/home-assistant/core

Scripts running in queued mode do not return response_variable data

opened 08:16AM - 04 Feb 25 UTC

stalakerob

### The problem Scripts running in queued mode do not return response_variable …data. I wrote a script that returns data to my conversation agent (LLM). The CA does not receive this data when the script runs in queued mode. When running in single mode it works. ### What version of Home Assistant Core has the issue? 2025.1.4 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue scripts ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml now_playing_on_ma: alias: "Get Now Playing Track Name from MA" description: 'This script is used to get the current playing song in Music Assistant based on a voice request. The tool requires no arguments. Use this tool whenever the user requests title or song information for the currently playing title on music assistant.' mode: queued sequence: - variables: response: title: Song from Band - stop: '' response_variable: response ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information When running the script in single mode it works.