Status Update
No update yet.
Comments
pa...@volume.co.uk
pa...@volume.co.uk
Project id: restaurant-phone-reservat-b9tt
Location: us-east1
Please have a look, this is a blocker for us.
Thank you!
pa...@volume.co.uk
Do we have an estimated time when these bugs will be solved, please?
pa...@volume.co.uk
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.
pa...@volume.co.uk
sa...@google.com
Hello Paolo,
Yes, this PIT is in P1 but the Dialogflow product team has shared that this is not in their immediate pipeline hence there is no ETA.
Description
What you would like to accomplish:
Need a code fix to solve the cache issue because of which newly restored and trained model is giving inconsistent results and sometimes returning results from previously restored model.
How this might work:
This might work with a code fix, as also mentioned by product engineers.
If applicable, reasons why alternative solutions are not sufficient:
The workaround: before sending a real request you should send ~5 warming up requests with small time intervals to force cache to update a model, provided still have some minor variation