Backend Workflow Not Updating Yes/No Fields (Match Result Logic Not Reflecting in Database)

Hey Bubblers :waving_hand:

I’m having trouble with a backend API workflow that updates yes/no fields in my Match data type, and I can’t figure out why it’s not working. Hoping someone can help point me in the right direction.

Here’s the setup:
• I have a backend workflow called process_matchresult.
• It receives parameters:
• match (thing)
• home_goals (number)
• away_goals (number)
• It’s supposed to update three fields in the Match data type:
• result_1x2_home (yes/no)
• result_1x2_draw (yes/no)
• result_1x2_away (yes/no)

Logic inside the workflow:

  1. It first resets all three result fields to “no.”
  2. Then sets the correct one to “yes” based on the score:
    • If home_goals > away_goals → result_1x2_home = yes
    • If home_goals = away_goals → result_1x2_draw = yes
    • If away_goals > home_goals → result_1x2_away = yes

What’s working:
• When I hit the “Settle Match” button on the front end, the goals_hometeam and goals_awayteam fields update correctly.
• The workflow is triggered successfully (I can see it run in the server logs).

What’s not working:
• None of the result_1x2_home, result_1x2_draw, or result_1x2_away fields get updated — they remain empty in App Data.
• I’ve confirmed the parameters are being sent (logs show the right goal values).
• Tried both static “yes” values and conditional logic (Only When), but no luck.

I’m wondering if:
• Boolean values can’t be updated this way from backend workflows?
• Or maybe I’m referencing the wrong fields (home_goals vs goals_hometeam)?
• Or perhaps the workflow order matters?

Would really appreciate any suggestions, screenshots, or example setups from anyone who has handled a similar match result logic before.

have you checked logs?
Sometimes “thing“ get missing. Especially in a recursive flows.
Make sure in logs you see a unique id of the db thing in which changes are being applied

Below is the log, the thing is not missing but it only stops after updating the result, the other action steps that makes changes of yes/no doesn’t run.

Schedule API Workflow process_matchResult

Anonymous user

1760202309421x124682143886084780

10/14/2025, 10:30:53 AM

Finished running action

WUs: 0.70

Duration: 29 ms

API Workflow:

process_matchresult

match:

1759497630336x439162439560555300

home_goals:

3

away_goals:

3

Scheduled date:

1760434252961

button_settle_match is clicked

Anonymous user

1760202309421x124682143886084780

10/14/2025, 10:30:53 AM

Finished running workflow

WUs: 2.32

5th row from last says “Anonymous user“ it means no user is detected. please pass the user as a parameter and then try.
if you are using “created by = current user “ it will not work
if you use “created by = user(parameter) “ it should work
change it in all searches being used in flow

Thank you for your help but I updated the parameter with user, but still it doesn’t work

See the below log after passing user parameter

button_settle_match is clicked

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:47 PM

Started running workflow

Make changes to Match…

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:47 PM

Running action

Thing to change:

1759497630336x439162439560555300

is_settled_

true

goals_hometeam

1

goals_awayteam

1

user

Make changes to Match…

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:47 PM

Finished running action

WUs: 0.62

Duration: 1 ms

Thing to change:

1759497630336x439162439560555300

is_settled_

true

goals_hometeam

1

goals_awayteam

1

user

Schedule API Workflow process_matchResult

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:47 PM

Running action

API Workflow:

process_matchresult

match:

1759497630336x439162439560555300

homegoals:

1

awaygoals:

1

Scheduled date:

1760449666970

Schedule API Workflow process_matchResult

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:48 PM

Finished running action

WUs: 0.70

Duration: 127 ms

API Workflow:

process_matchresult

match:

1759497630336x439162439560555300

homegoals:

1

awaygoals:

1

Scheduled date:

1760449666970

button_settle_match is clicked

yourstrulydboy@gmail.com

1758618430795x331494581933025100

10/14/2025, 2:47:48 PM

Finished running workflow

WUs: 1.82

Problem still persists?

Is the user data type part of your parameter?

This topic was automatically closed after 70 days. New replies are no longer allowed.