hey, maybe ur problem is a mismatched field name. the record might not even have a ‘uid’ field. check if your endpoint returns the intended id and adjust accordingly. good luck!
In my experience, these problems usually arise from an incorrect mapping between the record identifier and the field names returned. I once encountered a similar situation where the record’s unique id was not what I expected, and I overlooked the structure of the JSON response. Here, rather than assuming the ‘uid’ field is present in the record’s fields, it might be nested differently or named otherwise. I recommend verifying the response structure with some debug prints to better understand how Airtable is returning the data, which often reveals the mismatch.