Assigned
Status Update
No update yet.
Comments
ds...@google.com
ds...@google.com
an...@sada.com
I also have the same problem:
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
an...@sada.com Restricted
Restricted
ds...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
an...@sada.com
Please request the access, I can provide it
Description
-- Issue description (short summary) --
In Dialogflow CX integrated with Google Chat, the "waiting" message (e.g., "One moment please") is delayed and only displayed alongside the tool's backend response. This causes the end user to experience an unresponsive interaction for 2-3 minutes, with no indication that the tool is actively working in the backend
-- Steps to reproduce the issue (detailed description) --
Integrate Dialogflow CX with Google Chat.
1. Set up an agent where the system triggers a tool to perform a backend operation that takes 1-2 minutes.
2. Add a prompt to send a "One moment please" message before the tool completes its operation. So that end user is aware of the tool is working in the backend
3. Observe that the "One moment please" message is sent alongside the tool's final response rather than immediately.
-- Expected behavior --
The "waiting" message (e.g., "One moment please") should be displayed immediately when triggered the action, providing feedback to the end user that the system is actively working in the backend.
-- Actual behavior --
The "waiting" message is delayed and only displayed simultaneously with the tool's backend response, leaving the user with no indication of activity during the 2-3 minutes of tool processing.
-- Workarounds (if any) --
No current workarounds identified
-- Documentation consulted --
No guidance found on resolving this behavior.
-- Other information --