Update from source repository (workflow run: 24354653002) (PR #17097) (commit: 75c77fb980043e096b1a7d638be7fc6f0fd15ba8) (branch: 26.4.0.cl)

Author: GitHub Action Sync Bot

cloud/modules/ROOT/pages/notes-weekly.adoc

@@ -53,8 +53,8 @@
 
 The following release notes cover weekly changes to the ThoughtSpot Cloud release. These enhancements and fixes are automatically deployed to customer instances. For the latest monthly release notes see the xref:notes.adoc[{version} release notes].
 
-[#apr-11-2026]
-== April 11, 2026
+[#apr-13-2026]
+== April 13, 2026
 === Liveboards
 [cols="10%,90%", grid=none, frame=none]
 |====================
@@ -72,6 +72,32 @@ The following release notes cover weekly changes to the ThoughtSpot Cloud releas
 |[.badge.badge-fix-relnotes]#Fix#| Auto mode is now preserved as the Spotter data source across pages and new conversations, ensuring a consistent user experience.
 |====================
 
+[cols="10%,90%", grid=none, frame=none]
+|====================
+|[.badge.badge-fix-relnotes]#Fix#| Fixed an issue in Auto mode that caused follow‑up questions against a different model in the same conversation to intermittently fail. Cross‑model questioning within a single chat session now works as intended.
+|====================
+
+[cols="10%,90%", grid=none, frame=none]
+|====================
+|[.badge.badge-fix-relnotes]#Fix#| Fixed an issue where Spotter’s narrative insights could show monthly periods shifted one month earlier after a timezone change. Narratives now correctly reflect the actual month range returned by the query results.
+|====================
+
+[cols="10%,90%", grid=none, frame=none]
+|====================
+|[.badge.badge-fix-relnotes]#Fix#| Follow‑up queries in multi‑turn Spotter conversations through the `POST /api/rest/2.0/ai/agent/conversation/{conversation_identifier}/send` API endpoint now reliably generate fresh answers based on the latest user question.
+|====================
+
+[cols="10%,90%", grid=none, frame=none]
+|====================
+|[.badge.badge-fix-relnotes]#Fix#| Spotter 2 answers no longer surface random internal message IDs to users. Responses now reliably show clear summaries instead of backend identifiers.
+|====================
+
+[cols="10%,90%", grid=none, frame=none]
+|====================
+|[.badge.badge-fix-relnotes]#Enhancement#| Improved MCP connector error handling so misconfigured connectors are automatically hidden from end users and no longer appear as broken options. Admins now see clear, actionable error messages that explain what’s wrong and how to fix the connector configuration.
+|====================
+
+
 [#apr-06-2026]
 == April 6, 2026