# failure model_region ClientError: 404 NOT_FOUND. {'error': {'code': 404, 'message': 'Publisher model `projects/vertex-ai-experminent/locations/us-central1/publishers/google/models/gemini-3.8-flash` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region. For more information, see: https://docs.cloud.google.com/gemini-enterprise-agent- # failure app_name ValueError: App name docs_helper is not valid. It should either be the full ReasoningEngine resource name, or the reasoning engine id. # conversation 1 · session 4465463788115591168 > I run shipctl 1.x. How do I undo release r42 in production? call read_page {"page": "rollback"} result read_page ["page", "text"] answer In shipctl 1.x, use `shipctl release revert`: ```bash shipctl release revert r42 --env production ``` *(or `shipctl release revert r42` if your default environment is production).* Note that database migrations are not rolled back automatically; any migrations run by r42 must be reversed with a new migration. In shipctl 2.x, this was replaced by `shipctl rollback --env production --to `. # ingest returned in 0.03 s; search right after: 0 memories # searchable after about 4 s: - I run shipctl 1.x. # conversation 2 · session 3635675556772577280 > How do I undo the last production release? call load_memory {"query": "shipctl version"} call read_page {"page": "rollback"} result load_memory {"result": {"memories": [{"content": {"parts": [{"text": "I run shipctl 1.x."}], "role": "user"}, "custom_metadata": {}, "author": "user", "timestamp": "2026-10-22T01:31:50.920516+00:00"}]}} result read_page ["page", "text"] answer Since you are using shipctl 1.x, run: ```bash shipctl release revert ``` Specify the release identifier you want to revert to. Note that database migrations are not automatically rolled back, so any migrations run in the last release must be reversed with a new migration. # list_sessions for dana: 2 sessions