These are Airtable error messages that indicate that the permissions must be verified. If the extension stops working suddenly and you see an error message related to permissions or authorization, you can troubleshoot the problem by going through the possible reasons in this article.
Common error messages |
|
|
|
|
First steps
Before proceeding, make sure that you are logged in with Airtable using the account that is integrated with miniExtensions. Check this article on how to identify the account. Once you know the account, identify the role it has in the workspace:
Log in to Airtable with the account connected to miniExtensions and go to the workspaces where the tables you use reside. You'll see the role of your Airtable account in the right panel of the workspace:
Possible causes
No permission or read-only access in Airtable (most common)
Depending on how the permissions are configured in Airtable or how the base was shared with you, the account you use with miniExtensions could have restrictions at different levels. If you can't edit a record or field on Airtable, you won't be able to edit it on miniExtensions:
Base level (most common): Your Airtable account may have read-only access to the base. You'll need to have the owner, creator or editor role; if the role of the account in the workspace is read-only or commenter you need to ask a higher role to upgrade it.
Table level permissions. Verify that the tables your extensions use have edit permissions for the role of the connected account. Check this in the Edit table permissions option:
Field level. Some fields have restricted permissions. If you receive an error message when trying to edit a specific field, check the field configuration in Airtable through the Manage fields option.
💡Tip: This might be the reason you encounter the error randomly/intermittently in the same form or child form. You have to find the field that has this restriction and adjust it accordingly.
Record no longer exists
The "Invalid permissions, or the requested model was not found." error usually occurs when the form attempts to retrieve a non-existent record. Possible reasons include an incorrect URL or the record has already been deleted.
Browser Cache Issue
In some cases the "Invalid permissions, or the requested model was not found." error can be caused by an issue with the browser cache. You should first try logging out of miniExtensions and then logging back in, as this usually resolve this issue. If this does not work, please try opening our site in another browser, or in an incognito/private window. If this resolves the issue for you, you can clear your main browser's cache and cookies to resolve the problem.
Base missing from the Airtable integration
Make sure that the Airtable integration includes the base that you are trying to access. You can learn how to update your Airtable integration in this article.
Synced Table
You’re trying to set up the extension on a Synced table to edit (read-only) fields. Restrictions apply.
Legacy Site
Legacy Site
Invalid Personal Access Token
Our current site (web.miniextensions.com) does not use an API key or Personal Access Token at all since the connection is established in an entirely different manner (OAuth).
Users of our legacy site (app.miniextensions.com) need to switch to the Personal Access Token (PAT) system as explained in this article.
The PAT that is used to connect the legacy miniExtensions site to Airtable can become invalidated (unauthorized) in some cases:
The Airtable user account that created the PAT was deleted or deactivated
The Airtable user account that created the PAT no longer has access to the base
In these cases it is recommended to add a update the existing PAT following the steps shown here.