> For the complete documentation index, see [llms.txt](https://docs.agenticflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agenticflow.ai/changelog/office-hour-48-trigger-reliability-memory-and-ui-stability.md). # Office Hour #48: Gemini 3.5 Flash, Trigger Reliability & UI Stability ### 📺 Quick Recap Office Hour #48 brings a new model addition alongside a stability-focused release that resolves a full set of user-facing workflow and workspace issues affecting debugging accuracy, run traceability, connection discoverability, and mobile usability. This release includes: * **Gemini 3.5 Flash** added to the PixelML Provider And fixes for: * Workflow run detail inputs rendering incorrectly for integer fields * Workflow run provenance label mismatch on detail pages * `Test input` navigation from Workspace History routing to an invalid destination * OpenAI-compatible provider count/detail mismatch behavior * Marketplace mobile launcher overlap and accessibility issue * Trigger edit modal not reflecting saved schedule values * Workspace-wide agent memory retrieval issues 🎥 Watch the full session: {% embed url="" %} *** ### ✅ Release Highlights * **Gemini 3.5 Flash is now available via PixelML Provider.** Google's fast, cost-efficient multimodal model is now accessible directly in AgenticFlow — no extra setup required. * **Workflow run debugging is now more reliable.** Run details now display integer inputs correctly and preserve trigger provenance labels. * **History retest flow is now usable.** `Test input` now routes users to the correct workflow target. * **Connections are more discoverable and consistent.** OAuth categories and OpenAI-compatible provider views now align with expected management flows. * **Mobile Marketplace interactions are safer.** Floating launcher overlap and accessibility naming issues were addressed. * **Agent scheduling and memory continuity are improved.** Trigger Editor now reflects saved values, and memory retrieval works consistently in affected setups. ### 🔍 What Changed & Why #### 1. Gemini 3.5 Flash Now Available via PixelML Provider Google's **Gemini 3.5 Flash** is now available in AgenticFlow through the **PixelML Provider**. Gemini 3.5 Flash is a fast, cost-efficient multimodal model with a large context window — well suited for high-throughput workflows, document analysis, and tasks where response speed matters. To use it, open the Model Selector, select **PixelML** from the provider list, and choose **Gemini 3.5 Flash** from the model list. *** #### 2. Workflow Run Detail Now Correctly Displays Integer Inputs Workflow run detail pages could show some number fields as blank, even when valid values were used in the run. This made run reproduction and debugging less reliable because the UI did not reflect the actual input used to execute the run. Run detail now displays those number fields correctly in the Inputs card. **Before** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-6fcace1836a92f5c5223a38ef5ba102add3a82f9%2Foh48-before-issue-1-2-run-detail.png?alt=media) **After (current capture)** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-391acf69b6afd714f4b021e04fd5d0ba3df94c67%2Foh48-after-issue-1-2-run-detail.png?alt=media) #### 3. Workflow Run Detail Now Preserves API Key Trigger Provenance Some workflow runs triggered by API key were labeled as `Anonymous User` on the detail page, while History showed the correct trigger source. This provenance mismatch could mislead incident reviews, support handoff, and audit/debug workflows. Trigger labels are now consistent between History and Detail views. **Before** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-6fcace1836a92f5c5223a38ef5ba102add3a82f9%2Foh48-before-issue-1-2-run-detail.png?alt=media) **After (current capture)** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-391acf69b6afd714f4b021e04fd5d0ba3df94c67%2Foh48-after-issue-1-2-run-detail.png?alt=media) #### 4. Workspace History `Test input` Now Routes to a Usable Target From Workspace History, clicking `Test input` could route users to a page that returned `Workflow not found`. The action appeared available but opened an invalid destination, preventing users from quickly re-testing inputs from a run row. Navigation has been fixed so `Test input` opens a usable destination in workspace context. **Before** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-1b80c2899bbf48b302015e24a0860bf97f46b510%2Foh48-before-issue-4-test-input-broken.png?alt=media) **After (current capture)** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-c70b2cd688bfa131e55fa57c460b2d82322ea6b6%2Foh48-after-issue-4-test-input-target.png?alt=media) #### 5. OpenAI-Compatible Provider Management View Is Now Consistent with Reported State The Connections list could report OpenAI-compatible providers as connected, while the provider detail page showed no corresponding provider rows. This created a data-consistency gap between summary and detail views and made provider management unclear. The OpenAI-compatible provider surface has been aligned so list-level status and detail-level manageability are consistent. **Before** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-15a18c8012e16b32fba353d1d988930a05634cd9%2Foh48-before-issue-6-12-connections-list.png?alt=media) **After (current capture)** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-43674a0529daa7f4a56416b0b892cde9f15b4288%2Foh48-after-issue-12-openai-compatible-detail.png?alt=media) #### 6. Marketplace Mobile Launcher No Longer Obstructs Primary CTA On mobile viewport widths, the floating support/chat launcher could overlap the Marketplace template `Download` CTA, partially blocking tap area. The launcher button also lacked an accessible name, creating an accessibility issue on a primary acquisition surface. Mobile spacing and launcher accessibility semantics have been improved so the CTA remains unobstructed and launcher controls are screen-reader friendly. **Before** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-0491f70f86459d9bf88e3c601d83bf9c0bfcdb0f%2Foh48-before-issue-17-mobile-marketplace.png?alt=media) **After (current capture)** ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-a93c5ec5241f410d47122536ac227cdee4352519%2Foh48-after-issue-17-mobile-marketplace.png?alt=media) #### 7. Trigger Edit Modal Now Reflects Saved Selection When editing an existing scheduled trigger, the modal could open with default values instead of the saved trigger configuration. The outer agent view still showed the correct saved trigger, but modal initialization mismatch prevented confident editing and caused confusion about real run cadence. The Trigger Editor now opens with the saved schedule values so users always edit the true current setup. ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-521ed037a866fa661170f6bab40b5966a0e40ca5%2Foh48-trigger-edit-modal.png?alt=media) #### 8. Workspace-Wide Agent Memory Retrieval Restored In affected workspace scenarios, agents could miss stored memory context across conversations. The issue affected multiple agents in those workspaces and could require users to repeat context manually. Memory retrieval behavior has been improved so agents can consistently access stored context in ongoing threads. ![](https://487764224-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ3ppnJjAH1qBNXEYnDPA%2Fuploads%2Fgit-blob-6440533a09a205f67ff853aadf16b1075fb30e4a%2Foh48-workspace-wide-agent-memory.png?alt=media) *** ### 🐛 Bug Fixes Included * Fixed integer workflow inputs rendering as blank on run detail pages * Fixed API-key-triggered runs being mislabeled as `Anonymous User` on detail pages * Fixed `Test input` routing from Workspace History to invalid embed targets * Fixed OpenAI-compatible provider list/detail consistency for provider visibility and management * Fixed Marketplace mobile launcher overlap with primary `Download` CTA * Fixed missing accessibility naming for floating launcher controls on mobile surfaces * Fixed Trigger Editor modal initialization mismatch with saved schedule values * Fixed workspace-wide agent memory retrieval issues in affected setups *** #### 🚀 5 Workflow Blueprint Prompts Copy any of the prompts below into **Claude Code / Codex / Ishi** (with the **AgenticFlow CLI** installed) to deploy a fully working workflow in minutes — no manual node-wiring required. **1. Content Brief from URL** > Using the AgenticFlow CLI, deploy the content-brief blueprint. Source URL: . Target audience: early-stage founders. Content goal: rank for keyword "how to find startup ideas". > > Deploy, run once, show me the full brief including angle, outline, and SEO keywords. > > Leave the workflow deployed. Print the Web UI link.\ > One-line note: why this rung of the composition ladder? *** **2. Pricing Page Analyser** > Using the AgenticFlow CLI, deploy the pricing-page-analyser blueprint. Analyse . > > Deploy, run once, show me the tiers table, pricing psychology breakdown, and conversion optimisation checklist. > > Leave the workflow deployed. Print the Web UI link.\ > One-line note: why this rung of the composition ladder? *** **3. Onboarding Email Sequence** > Using the AgenticFlow CLI, deploy the onboarding-email-sequence blueprint. Use these inputs: > > Product: Notion — an all-in-one workspace for notes, docs, tasks, and databases.\ > User persona: freelance designer who just signed up for a free trial.\ > Aha moment: first project page created with a template.\ > Sender: The Notion Team > > Deploy, run once, show me all 5 emails (Day 0 to Day 14). > > Leave the workflow deployed. Print the Web UI link.\ > One-line note: why this rung of the composition ladder? *** **4. SEO Meta Writer** > Using the AgenticFlow CLI, deploy the seo-meta-writer blueprint. Page URL: . Primary keyword: "product analytics". Brand: PostHog. > > Deploy, run once, show me the title tag options, meta descriptions, OG copy, and H1 recommendation. > > Leave the workflow deployed. Print the Web UI link.\ > One-line note: why this rung of the composition ladder? *** **5. Performance Review Drafter** > Using the AgenticFlow CLI, deploy the perf-review-drafter blueprint. Use these inputs: > > Employee: Alex Chen | Role: Product Designer | Period: Q1 2025\ > Achievements: Led onboarding redesign (+22% activation). Delivered 3 feature designs on time. Ran 8 user research sessions.\ > Areas to improve: Needs clearer stakeholder communication. Could be more proactive cross-team.\ > Goals next period: Ship mobile redesign by Q2. Run monthly design critiques.\ > Rating: Exceeds expectations | Reviewer: Sarah Manager | Email: > > Deploy, run once, show me the full review and confirm the email was sent. > > Leave the workflow deployed. Print the Web UI link.\ > One-line note: why this rung of the composition ladder? *** ### 🔗 Get Started * **Try AgenticFlow free:** * **Latest changelog:** * **Join our Discord:** * **Found a bug?** Email with a reproducible case.