Back end workflow not working?

I am doing a test project to learn about Bubble’s capabilities, and I can’t figure out something.

The test project is a Yelp clone. So basically, I have a parent “Market” object with child “Review” objects. For relevance to this question, each Review object has a numeric “Rating” field and each “Market” has a numeric “MapIcon” field.

I’d like to create a backend workflow such that on ANY change to a child Review object, e.g.,:

  • a new Review is created
  • an existing Review is destroyed
  • an existing Review is updated

There is a calculation run to automatically calculate MapIcon and save that to the parent Market.

I want this to be a backend workflow to ensure that it runs no matter how the Review is modified (either in front end by user or directly by admin in the backend data table).

I made the backend workflow, jowever, it appears to not have worked see video: Loom Message - 21 November 2024 | Loom

One thing that I wonder… you’ll see that when a Review is updated (old Rating is not same as new Rating), the workflow is updating the Market. It’s looking for the Market based on unique id = Review now’s Parent Market’s unique id. I DID set this, but notice on the Loom at 0:17, how when I click to toggle this out, it shows as RED, as if the search query was incorrectly formed, but when I click on the RED text, the correctly formed query appears… this isn’t the first time I’ve seen this, I’m struggling to figure out what this UI means?

In any case, in the rest of the Loom you see me going into App Data to make a modification on a Review, which succeeds, and then you see me going into Server Logs, it looks like the backend workflow DID run, but however, the final update doesn’t work, as the Market doesn’t have MapIcon = 4 (for now I’m just doing any changes to Review Ratings causes the MapIcon to equal 4, rather than running an average calculation, that will be next)

Also I checked, scheduler is not paused.

Not Following all the steps but you shouldn’t be using the market’s UID as the review seems to be linked to the market already…