# Lookup & Formula Fields Not Updating on Record Creation

**URL:** <https://community.noloco.io/t/lookup-formula-fields-not-updating-on-record-creation/2421>\
**Category:** Ask for Help\
**Created:** [April 17, 2026, 1:36pm UTC](https://community.noloco.io/t/lookup-formula-fields-not-updating-on-record-creation/2421 "2026-04-17T13:36:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ariel-k](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@ariel-k](https://community.noloco.io/u/ariel-k)\
**Post date:** [April 17, 2026, 1:36pm UTC](https://community.noloco.io/t/lookup-formula-fields-not-updating-on-record-creation/2421/1 "2026-04-17T13:36:50Z")

</div>

I’m writing to ask about an issue we’ve been experiencing with lookup and formula fields not updating reliably in our app.

We’re using Noloco Tables as our data source. The issue: lookup fields and formula fields that reference lookups often do not recalculate when a new record is created or an existing record is updated via an action or integration. The fields only update after we manually re-open and save the affected record.

This is causing data integrity issues for us, as we rely on these computed fields for case management workflows.

A few specifics:

- It affects both lookup fields and formulas that reference lookup values
- The data in the source/related table is correct — it’s the computed field that isn’t refreshing

Is this a broader platform issue? Interested in understanding:

1. Whether this is a known bug with a fix in progress
2. Any reliable workaround in the meantime
3. Whether there’s a way to force recalculation programmatically

---

<div class="post-metadata">

**Author:** ![Neervig](https://avatars.discourse-cdn.com/v4/letter/n/8491ac/32.png) [@Neervig](https://community.noloco.io/u/Neervig)\
**Post date:** [April 19, 2026, 12:27pm UTC](https://community.noloco.io/t/lookup-formula-fields-not-updating-on-record-creation/2421/2 "2026-04-19T12:27:31Z")

</div>

We’ve had the same issue. But after they published a fix, I think it was last week, then we haven’t experienced it on new records.
