Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
What you would like to accomplish:
Ready to query
status is only useful for the initial training and causes confusion if you're querying with the latest trained details or notHow this might work:
If applicable, reasons why alternative solutions are not sufficient:
Ready to query
status that indicates the app is ready to be used(after its initial training) will continue to stay there if your model was re-indexed, this makes it so users don't know if the model that is currently ready to query has the latest changes implemented and forces them to periodically check hoping that the training occurred somewhere within the1-5 days
suggestion given by the cloud console.Other information (workarounds you have tried, documentation consulted, etc):
[1]https://cloud.google.com/generative-ai-app-builder/docs/reference/rest/v1alpha/projects.locations.collections.engines#trainingstate