Overview
Skyvia interacts with Salesforce via its API. During a backup or replication operation, you may encounter errors caused by certain limitations or behaviors specific to the Salesforce API.
Why This Happens
When Skyvia performs a backup or replication, it queries all data from Salesforce using a SELECT query. However, some Salesforce objects require a WHERE condition in the query. A simple SELECT * FROM Table is not valid for these objects.
These objects require specific filter conditions. The error message typically includes details about the required filters. Common examples:
| Object | Required Filter |
|---|
FlowVariableView | Filter on a reified column is required: [FlowVersionViewId, DurableId]
|
ContentFolderItem | Filter by Id or ParentContentFolderId using equals or IN operator |
| Access-level objects | Can select only RecordId, a Has*Access field, and MaxAccessLevel |
FlexQueueItem | WHERE clause must contain a JobType field expression |
For additional context, see How to query FieldDefinition records on Salesforce StackExchange.
Why Skyvia Cannot Add Filters Automatically
Objects with such restrictions are generally system tables that contain metadata about other objects, columns, or service information, not user data. Each object has its own specific filter requirements, and most filters are based on specific ID values. For this reason, Skyvia cannot add these filters automatically.
Note: These tables are typically read-only and cannot be used in a restore operation.
Resolution
- Recommended: Exclude these objects from the backup if they are not required for your use case.
- If the objects are required: Manually add filters to the relevant tasks in your backup or replication configuration.
Related Articles
Salesforce API errors: TotalRequests Limit Exceeded / ApiBatchItems Limit Exceeded
Overview The TotalRequests Limit Exceeded and ApiBatchItems Limit Exceeded errors are Salesforce-side governor limits. They are not related to Skyvia's own limits. When these limits are reached, Salesforce rejects all further API calls until the ...
Resolving ActiveCampaign Backup Errors (403 Forbidden)
Overview Sometimes, when running an ActiveCampaign backup, users may encounter the following error: The remote server returned an error: (403) Forbidden This happens when the ActiveCampaign API receives too many requests in a short period, especially ...
Skyvia Query: Verify Data in Your Connection
Overview Skyvia Query allows you to browse and verify data in any connected data source directly from the Skyvia interface, without writing complex scripts or using third-party tools. You can use the visual Builder view or write custom SQL ...
Salesforce Report exports only 2000 records
Overview When using Salesforce Reports as a data source in Skyvia, the export is limited to the first 2,000 rows. This is not a Skyvia limitation — it is a hard restriction imposed by the Salesforce Run Report API, which Skyvia uses to retrieve ...
Salesforce: Inactive User Error
Overview The "inactive user" error occurs at the Salesforce connection level in Skyvia. It means that the Salesforce user account used for the connection is inactive or no longer valid, so Salesforce blocks API authentication. As a result, Skyvia ...