Data Crawling Updates for Migrated Content Connectors

What changes

Migrated content connectors appear under Content (new architecture) in Moveworks Setup → Data Ingestion → Data Crawling. As these connectors move to the new ingestion architecture, their troubleshooting view changes to failed API request counts and a View Failed Logs action.

The updated view helps administrators investigate failed source-system requests. It is an interim monitoring experience and does not provide the previous full-refresh and incremental run history or an overall crawl-health assessment.

Availability

The updated view is released. Content (new architecture) appears automatically for connectors after they are migrated to the new ingestion architecture for your organization. The connector migration determines when you see the section; you do not need to enable the view yourself.

Your organization may have connectors under both Content and Content (new architecture) while migrations continue. Follow the instructions for the section where your connector appears.

How to investigate a failed request

1. Open Data Crawling in Moveworks Setup and expand Content (new architecture) using View Crawls.
2. Locate your connector under the relevant resource group and select View Failed Logs.
3. Review the Timestamp, Error Code, Error Message, and API Request. Filter by error code to narrow the results.
4. Use the request details to investigate source-system access or configuration with your administrator. Contact Moveworks Support if the issue remains unexplained.

What the view can and cannot tell you

Crawl Health displays Not applicable. This means the section does not provide a crawl-health assessment; it is not a Healthy or Unhealthy result. Full-refresh and incremental run charts, individual run details, and per-run record inspection are unavailable in this view.

Failure counts represent logged API-request events. Multiple entries can refer to the same endpoint or problem. Counts do not measure missing documents or unique unresolved issues, and historical failures may not describe the connector's current state.

An empty failed-request table does not establish complete or current ingestion. Use the existing record-level inspection tools in Control Center to investigate a particular article or file. Contact Moveworks Support for unresolved questions about missing or stale content.

Customer action

You do not need to recreate your connectors or move them between sections. For connectors that appear under Content (new architecture), use the updated failed-request investigation workflow. Connectors under Content continue to use the existing run-based monitoring experience.

Documentation

See the Data Crawling View documentation.