Troubleshooting & FAQs - Custom Connector

Troubleshooting

For common issues that apply to all connectors — authentication failures, syncs stuck or not progressing, no documents indexed, stale permissions — see Troubleshooting - Enterprise Search Connectors.

Recent changes to a JSON file in Amazon S3 aren't showing up

Symptoms: A JSON object was added, updated, or deleted in a configured bucket, but the change doesn't appear in search right away.

Cause: Amazon S3 does not support incremental sync in this release — content changes are only picked up at the next full sync (daily by default, or triggered manually).

Resolution:

1. Trigger a manual full sync from Enterprise Search → Custom Connector → Status.

2. Otherwise, wait for the next scheduled daily full sync.

Frequently asked questions

Common questions about sync frequency, deletions, audience filters, and throttling are answered in Troubleshooting - Enterprise Search Connectors. Security, privacy, and data questions are answered in Data & Security - Enterprise Search Connectors.

Custom Connector-specific FAQs

Q1. Can one connector instance index both Amazon S3 and SharePoint Online?
No. Each Custom Connector instance connects to exactly one source type, chosen when the connector is created. To index both, create two separate connector instances.

Q2. Can I change the source type after creating the connector?
No. The source type is fixed at creation. To switch source types, create a new Custom Connector instance and remove the old one once you've verified the new one is syncing correctly.

Q3. Are Amazon S3 bucket policies or SharePoint item permissions enforced in search results?
No. This connector does not sync or enforce source-system permissions for either source type. All indexed content is visible to any Simpplr user with access to this connector. Use Simpplr Audiences to control who can see this connector's results.

Q4. What happens to a JSON record in Amazon S3 that's missing required fields like id or title after mapping?
It is skipped during sync and not indexed. The sync itself continues and does not fail because of it.

Q6. How long does the initial sync take?
It depends on the number of objects in your configured Amazon S3 buckets or the number of files in your configured SharePoint sites. Larger buckets or sites take proportionally longer; see Content, Sync & Limitations - Custom Connector for sync scheduling detail.