Skip to content

Repost: AI Agents return null when inside of Action Blocks #5814 #5984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
dominikmucklow opened this issue Jun 12, 2025 · 1 comment
Closed
2 tasks done
Assignees

Comments

@dominikmucklow
Copy link

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

#5814

This is a confirmed bug, only reposting because no further action has been taken in 1 month.

An AI Agent that has been formatted to return JSON will only work as a normal action, but not within an Action Block. It will return 'null' inside of the Action Block.

Expected Behavior

The AI Agent should return a non-null response even if it is nested inside of an Action Block.

Steps to Reproduce

  1. Create an AI Agent with a JSON output
  2. Place Agent inside of an Action Block with correct input parameters
  3. When the Action Block is triggered, the output will be null

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4kysmB34ZgocdG1s/Lbe0xgj07C1ggTLJEoetxc0gbfe/4EZkMY8mkVxNpTdyzaH52HlaInk0C083GjeH1KPkVHziCc755wqV6ZhPPbFu5MI+YCc+8end5GtxXC0fG0cGJkQolNrZtZV0uw2C6GuiXEj+Cf9qOYwx5e6fDbOY=

Visual documentation

Screen.Recording.2025-05-13.at.12.09.51.mov

Environment

- FlutterFlow version: v5.4.9
- Platform: Web
- Browser name and version: Chrome 135.0.7049.95
- Operating system and version affected: macOS Sonoma

Additional Information

This occurs regardless of whether in Test Mode or deployed as a Web app.
It occurs on any Google Gemini model (OpenAI was not tested).

Image

@dominikmucklow dominikmucklow added the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 12, 2025
@Alezanello Alezanello self-assigned this Jun 12, 2025
Copy link
Collaborator

Hello!

Thank you for your patience. The other issue is still open, and our team is actively working on it. We understand it can be frustrating when something isn't yet live in production, and we truly appreciate your understanding.

Rest assured, the issue will be marked as closed once the fix is completed and deployed to production.

@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 12, 2025
@Alezanello Alezanello closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants