Step 4: Connector Run Errors

Entity Errors

Why is my field value invalid?

This is likely not an issue with the connector itself, but with the value being mapped to the field.

Some things to check:

• Refer to the settings on the field in question to check that the input data is valid (go to Knowledge Graph > Configuration > Fields and click on the field to view settings).
• Is there an accidental trailing or leading space? If so, try using a Remove Characters transform.
• Have you provided the API name of the field (not the display name)? API names for each field are displayed on Knowledge Graph > Configuration > Fields.

See the Mapping Data to Fields section of this guide for information about specific field behavior.

Why do I see fewer entities than expected?

Entities could be missing from a run for various reasons, including:

• Filter Rows transform: This may filter out entities in the response
• Run errors: If an error occurred on a transform or in fetching the data, some entities may be missing
• Pagination: Incorrect pagination settings may cause missing data. Confirm you have the correct pagination settings by paginating through the preview table.
• Source data: Does the source data definitely contain the missing entities? Are there any filter or query parameters that may have excluded some items?

What does it mean that I can’t update the entity type?

Updates to entity types are not supported via Connectors.

If an entity is failing due to the entity type, it’s likely that the value for the entity type (either as applied on the connector configuration, or as it is mapped, if the connector is ingesting multiple entity types) is different from the type of the existing entity with the ID you are attempting to map to.

Run Errors

My request timed out - what should I do?

The system will wait 30 seconds to receive a response before timing out. In order to reduce the time of execution, you can:

• Reduce the total size of the response (e.g., specify fewer items to return per page)
• Reduce the size of each object in the response (e.g., add query parameters to only return certain fields for each entity)

I hit a rate limit - what should I do?

To avoid hitting a rate limit, specify a maximum number of requests to return per hour/minute/second.

Why did my transform fail?

A transform may fail for a variety of reasons:

• Date/Time transforms may fail if the actual data does not match that of the specified input format. Confirm that all data is formatted properly, or apply conditions to ensure that the transform is only executed on expected data formats.
• For Function transforms, check the developer logs to see why a function may have failed.
• Is there a trailing and/or leading space? (If so, try using a Remove Characters transform. )
• Map Publisher Categories transforms will fail if a category or attribute is not eligible in Yext. Remove the category/attribute from the data set, and reach out to your Yext Account Team if you think it should be supported in Yext.

See the Transform Options reference for more information about specific transforms.

Why is there data missing from my crawler connector run?

See the Troubleshoot a Crawler Connector guide for steps on troubleshooting crawler connectors.

Function Errors

Why is my function failing?

Navigate to the Function Logs table (under Developer > Logs) to view all function executions. Use the appropriate filters to view the executions in question, and notice any error messages.

If the error messaging does not provide a clear answer, you can:

• Look at the function code in the Admin Console (under Developer > Admin Console)
• Add more console logging to see where the error is occurring
• Test the function locally, using the values that are failing as test values

How can I troubleshoot a function on a row?

There are two main reasons a function on a row might fail:

• The output type must be an object, an array of objects, or undefined, which removes the row entirely
• Function transforms can only be invoked for 10 seconds per row

Check the Function Logs (under Developer > Logs) to see any error messaging and more details about each invocation.

Pagination (Pull from API)

Why am I only seeing the first page of results returned from the API?

If the pagination settings are incorrect, then the connector is unable to fetch pages past the first page. Refer to the Pull from API reference to confirm proper configuration.

Troubleshooting Tips

Issues with a specific entity

Try to view that specific entity in the preview table and observe how it responds to transforms and mappings. You can do this by paginating through the preview table.

• For Pull from API connectors: filter to a specific row by adding a query parameter to the API request
• For Crawler connectors: in the URL settings, input the crawled page URL you would like to see results for

Transformed field values

If you can’t figure out why a mapped field value is failing (specifically due to a transform), try to narrow down which part of the value is failing. For example, if a field containing a paragraph or list undergoes a transform that fails, try to determine which sentence or item is causing the issue.

You can do this with two different transforms: * Find and Replace the entire cell (regex: ^.*$) with different parts of the value. See how the connector transforms and mappings respond to each part. * Use Add Column to add a column containing parts of the failing field values. Apply the connector transforms and mappings to the new “fake” column and see how the connector transforms and mappings respond.