This message was deleted.

The basic rule with this is that if the update happens in Airtable, it'll take 15 mins to sync back to Stacker. A way out of this is to trigger an update in Stacker to "refresh" the record. This way the Airtable updates will be immediately synched. For e.g. If an automation in Airtable creates a record and it is linked to the record you are viewing in Stacker, the linked field will not show the newly created record till 15 min sync is done.

Action/Event originated on Stacker = instant Action/Event originated anywhere else = 15min

thanks @millions-army-64326 @clever-art-10420. So the workaround that @sticky-night-20812 created was to create a ‘Sync’ button, when clicked updates a checkbox immediately in stacker, which in turns triggers a refresh of the record to include the values created in airtable as a result of automations etc. Is this correct? Does this reliably refresh all values when triggered?

This refreshes the values of only the record that had the check box. If you wanted to pull in changes in other records, from same table or different tables, as part of this then that won't work

@witty-room-67787 As Ruchika said, it’s reliable for the current record only, not for other records. It’s still very useful in some cases, although doesn’t cover all my needs.

Cheers guys. I will play around with it and find the edges. I'm finding that figures in charts represented as a number (sum of fields) update on a browser refresh, however the same fields are bound to 15min sync when rendered in a highlights widget - see image (field = Live Actions). What's the deal there?

@witty-room-67787 it could be stacker use a different data pipeline for rendering that stuff/State management life cycle. Given the Refresh Action Button -> Checkbox is a community workaround it wouldn’t surprise me that this was at odds with other Stacker features. I think the expectation that when the AT record in Stacker is updated (doesn’t matter how/when it happens) Then all components that rely on that state should update/rerender. Including Highlight Sections @gorgeous-queen-48490 This sounds like a bug in the implementation of the highlights section

Thank you for flagging @clever-art-10420 – will investigate!