It would be beneficial that when an action is performed on a block (Creation, Update, or Deletion), other blocks linked through data cross-referencing in the database automatically switch to “update mode”, awaiting validation.
Indeed, these blocks are interconnected: modifying, adding, or deleting data in one block can impact other blocks that rely on the same data.
Instead of immediately refreshing the page and executing updates in real-time, it would be preferable to adopt a deferred update mechanism triggered by a specific event, such as a checkbox in Airtable.
Executing updates in real-time could cause issues if some blocks require more time to complete their update process. If an update starts but hasn’t finished executing, the displayed data might be outdated or incomplete, leading to inconsistencies for the user.
To prevent this, it is essential that when an action is performed on a block, it is temporarily hidden and displays an indicator stating “Updating in progress”. The block should only reappear once the update is complete and the data is correctly refreshed.
This approach would allow users to continue working freely on the same page, within other blocks, without being interrupted by background automation processes while ensuring data consistency across all affected blocks.