Group field inconsistently not saving from API workflow (Anthropic → Bubble)

Need help
1

I’m running into a very specific issue where one field (group) is inconsistently not making it into my database, even though Bubble clearly receives it.

Setup

  1. API Call (Anthropic)

    I call Anthropic with a tool schema that returns a list of accounts with the following fields:

    status, type, group, subgroup, name, balance

  1. Workflow

Step 1: API Call

Returns:

Result of step 1’s content:first item’s input accounts

Step 2: Schedule API Workflow on a list

  • Type of things: anthropic_onboarding input account

  • List to run on:

    Result of step 1’s content:first item’s input accounts

  • API Workflow: create_onboarding_account

Parameters passed:

status = This item’s status

type = This item’s type

group = This item’s group

sub group = This item’s subgroup

name = This item’s name

balance = This item’s balance

group_raw = This item’s group

Step 3: Backend Workflow (create_onboarding_account)

Parameters:

status (type: Status option set)

type (type: Type option set)

group (type: Group option set)

sub group (text)

name (text)

balance (number)

group_raw (text)

Then:

Create a new onboarding_accounts

status_option = status

type_option = type

group_option = group

sub_group = sub group

name = name

balance = balance

group_raw = group_raw

The Problem

In Bubble server logs, I can clearly see:

“group”: “property”

“_api_c2_group”: “Property”

So Bubble is receiving the correct value.

And for some rows, it works perfectly:

group_optioninvestment

group_optionother

group_optionproperty

BUT for certain rows (especially House / Mortgage cases), I get:

group_option (blank)

group_raw (blank)

Even though:

  • the request payload shows “group”: “property”

  • _api_c2_group is present

  • other fields (status, type, name, subgroup) all save correctly

Key Observations

  • This happens only for specific rows (e.g. House / Mortgage)

  • In the same API response, other rows populate group fine

  • The issue is not global

  • The API clearly returns the correct group

  • Bubble clearly receives it

  • But the value disappears before being saved (or during mapping)

Additional Clue

In the request payload:

“group”: “property”

“group_raw”: “”

So group is populated, but group_raw is already blank before the create step runs.

What I Need Help With

Why would:

group = This item’s group

group_raw = This item’s group

result in:

  • group being populated

  • but group_raw being blank

  • and sometimes group_option also ending up blank for specific rows

…even though the API response clearly includes the value?

Core Question

Where in Bubble could a field:

  • exist in the API response

  • appear in the workflow request payload

  • but not survive into the final database row (for only certain items in the list)?

What I’ve Ruled Out

  • Anthropic response issue (confirmed correct)

  • Option set mismatch (works for other rows)

  • Global workflow error (only affects some rows)

If anyone has seen behavior like this with I’d really appreciate any insight.

1 Like
2

Your option display value in bubble db may not match perfectly with what the api call returns, or your current option display does match perfectly, but you may have changed it from an original value.

House is not same as house…if not perfect match it will not find it.

3

Ran into almost the same thing with Bubble, and it drove me crazy because logs showed everything correctly but the DB still ended up with blanks. Turned out to be tiny mismatches in option set values, even capitalization or previously renamed entries break the mapping silently. Had similar headaches while wiring flows in Phonexa, where one inconsistent value can quietly kill the whole pipeline.

1 Like
4

Had the same issue, I just save as text field and then do a Get all options filtered where display = text: first item

5

This is usually a timing/data source issue.

Check if the group actually has data at the exact moment the workflow runs — especially if you’re using “Display data” right before saving.

Also confirm you’re referencing the correct source (Group’s thing vs Parent group’s thing) and that privacy rules aren’t blocking that field.

Inconsistent behavior usually means the data isn’t always available when the save happens.