IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Using connectors Troubleshooting connectors »

› ›

Connector known issues

edit

Connector known issues

edit

Connector service

edit

The connector service has the following known issues:

The connector service will fail to sync when the connector tries to fetch more more than 2,147,483,647 (2^31-1) documents from a data source

A workaround is to manually partition the data to be synced using multiple search indices.
Custom scheduling might break when upgrading from version 8.6 or earlier.

If you encounter the error 'custom_schedule_triggered': undefined method 'each' for nil:NilClass (NoMethodError), it means the custom scheduling feature migration failed. You can use the following manual workaround:
```
POST /.elastic-connectors/_update/<connector-id>
{
  "doc": {
    "custom_scheduling": {}
  }
}
```
This error can appear on Connectors or Crawlers that aren’t the cause of the issue. If the error continues, try running the above command for every document in the .elastic-connectors index.
Connectors upgrading from 8.7 or earlier can be missing configuration fields

A connector that was created prior to 8.8 can sometimes be missing configuration fields. This is a known issue for the MySQL connector but could also affect other connectors.

If the connector client raises the error Connector for <connector_id> has missing configuration fields: <field_a>, <field_b>..., you can resolve the error by manually adding the missing configuration fields via the Dev Tools. Only the following two field properties are required, as the rest will be autopopulated by the connector client:
- type: one of str, int, bool, or list
- value: any value, as long as it is of the correct type (list type values should be saved as comma-separated strings)
```
POST /.elastic-connectors/_update/<connector_id>
{
  "doc" : {
    "configuration": {
      <field_a>: {
        "type": "str",
        "value": ""
      },
      <field_b>: {
        "type": "bool",
        "value": false
      },
      <field_c>: {
        "type": "int",
        "value": 1
      },
      <field_d>: {
        "type": "list",
        "value": "a,b"
      }
    }
  }
}
```
Python connectors that upgraded from *8.7.1 will report document volumes in gigabytes (GB) instead of megabytes (MB)*

As a result, true document volume will be under-reported by a factor of 1024.
The following native connectors will not run correctly on Elastic Cloud in 8.9.0. They are still available as self-managed connector clients.

Upgrading Enterprise Search from versions `⇐`8.5.x to versions `>=`8.9.x will fail if Connectors or Elastic Crawler were used

In 8.5, Connectors and Elastic Crawler created records in .elastic-connectors-sync-jobs with a pre-GA structure that is incompatible with the GA document schema.

As a result, a migration added in 8.9.0 will fail with the error:

Status: [Failed] Applying Actastic Migration: <ChangeSchedulingAndAddJobTypeAndSyncCursorToConnectors version=20230526133312>: Error = NoMethodError: undefined method `[]=' for nil:NilClass

Additionally, after this error appears 20 times, a second error will begin to appear:

Status: [Failed] Applying Actastic Migration: <ChangeSchedulingAndAddJobTypeAndSyncCursorToConnectors version=20230526133312>: Error = Swiftype::ES::UnknownEsError: [1:2807] failed to parse: Limit of mapping depth [20] has been exceeded due to object field [scheduling.full.full.full.full.full.full.full.full.full.full.full.full.full.full.full.full.full.full.access_control]

To work around these issues and move forward with upgrading, you should remove the .elastic-connectors* indices.

DELETE .elastic-connectors*

Individual connector known issues

edit

Individual connectors may have additional known issues. Refer to each connector’s reference documentation for connector-specific known issues.

Workplace Search connector known issues

edit

For Workplace Search connectors, see the Workplace Search documentation.

« Using connectors Troubleshooting connectors »