# \[Solved\] Airtable "get value from cell" block returns cached data \[June 2022\] **URL:** \ **Category:** Issues / Bugs\ **Tags:** bugs\ **Created:** [June 3, 2022, 2:04pm UTC](https://community.thunkable.com/t/solved-airtable-get-value-from-cell-block-returns-cached-data-june-2022/1909356 "2022-06-03T14:04:37Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![slothball](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@slothball](https://community.thunkable.com/u/slothball)\ **Post date:** [October 22, 2024, 12:28pm UTC](https://community.thunkable.com/t/solved-airtable-get-value-from-cell-block-returns-cached-data-june-2022/1909356/19 "2024-10-22T12:28:45Z")
Hi @ioannis - thanks for this explanation, but I am now confused! My app originally used the Web API blocks for my app. I had a question about about this, which you answered here: > [@Airtable's API keys will be deprecated by Airtable](https://community.thunkable.com/t/airtables-api-keys-will-be-deprecated-by-airtable/2805223/10): > > Hello @slothball The Airtable blocks you have are connected to Airtable via API key at the moment. This means that needs to be replaced with the [Data Sources blocks](https://docs.thunkable.com/blocks/app-features/data-sources-blocks). ​ As a result, I have been reworking the part of my app that relates to using Airtable and then I stumbled across this problem with the cache, which is really problematic. Am I right to understand that I could actually retain my former WebAPI blocks for Airbase but use this “authorisation header” to make it work? If so, do I have to insert this header before each older Web API blocks to make it work? Thanks for your help - I have managed to get really confused with this, when it seems the solution to my original problem might be quite easy? --- _[View the full topic](https://community.thunkable.com/t/solved-airtable-get-value-from-cell-block-returns-cached-data-june-2022/1909356)._