Help

Save the date! Join us on October 16 for our Product Ops launch event. Register here.

Infinite error after running extension

Topic Labels: Extensions
574 1
cancel
Showing results for 
Search instead for 
Did you mean: 
guillnejs
5 - Automation Enthusiast
5 - Automation Enthusiast

I have an extensions that use useCursor, useLoadable, and useWacthable. I am able to run an extension application and get the correct entry id to generate what I need to. After I have run the extension and click on a different cell I get tons off errors in the console that looks something like this. 

 

 

~Uncaught (in promise) Error: comment count out of sync
at RecordStore. _ loadCellValuesInFieldIdsAsync$ (bundle. js 1: 180883)
at tryCatch (bundle js:1:1444931)
at Generator. invoke las invoke] (bundle.js: 1: 1444536)
at Generator.next (bundle.js: 1:1445835)
at tryCatch (bundle js:1:1444931)
at invoke (bundle. js:1:1446108)
at bundle.js: 1:1446340
loadCellValuesInFieldIdsAsync$ @ bundle.js: 1 tryCatch
@ bundle.js:1
invoke
@ bundle.js:1
(anonymous )
@ bundle.js:1
tryCatch
@ bundle.js:1
invoke
@ bundle.js: 1
(anonymous )
@ bundle.js:1
8 Error: comment count out of sync
at RecordStore..
_loadCellValuesInFieldIdsAsync$ (bundle.js: 1:180883)
at tryCatch (bundle.js: 1:1444931)
at Generator. invoke las invoke] (bundle.is: 1:1444536)
at Generator. next (bundle,js: 1:1445835)
at tryCatch (bundle.js: 1:1444931)
at invoke (bundle is:1:1446108)
at bundle.js: 1:1446340 (anonymous
@ bundle.js:1
Promise.catch (async)
useLoadable _useUnwatchedRecordQueryResult useRecordById
EditorGuard
Th
@ bundle_js:1
@ bundle is:1
@ bundle.is:1
@ bundle.is:1
@ bundle,is:1
si
@ bundle.is:1
gk
@ bundle.js:1
fk
@ bundle.js:1
Zi
@ bundle.js:1
Li
@ bundle.is:1
(anonymous )
@ bundle.is:1
exports. unstable_runWithPriority @ bundle.jsH1 fg
@ bundle.is:1
ia
@ bundle.is:1

 

 


I am not exactly sure what it could be does anyone have any idea?

1 Reply 1
SilverTaza
6 - Interface Innovator
6 - Interface Innovator

I think it's a bug on the Airtable side. I also faced this, and the only solution I came up with at the time is just try avoid your application do anything useful just after updating a cell for a while.