# YouTube Limitations and Troubleshooting

This topic contains YouTube limitations and troubleshooting tips.

## YouTube Limitations

### Google API Credit Quota

- If you go over your allocation, the connector fails.
- Ingesting transcripts significantly inflates your [Google API credit rate](https://developers.google.com/youtube/v3/determine_quota_cost) consumption.
- All YouTube connectors you create use the same pool of credits for [Google API credit rate](https://developers.google.com/youtube/v3/determine_quota_cost) consumption.
- You can ingest about 25–30 videos with captions within a standard quota. This range can vary.
- Reaching the API credit limit [quota](https://developers.google.com/youtube/v3/guides/quota_and_compliance_audits) threshold causes the connector to fail.
- You can optionally [increase](https://support.google.com/youtube/contact/yt_api_form) your Google API quota for YouTube.

### YouTube Videos

- Only public videos in channels you own are ingested.
- If you need someone else’s videos, make sure you co-own their channel or have them create the connector for you.
- If the content you want to ingest is private, change the Private label to Public.

### Google API Refresh Token

- By default, unless you don't create an auto-regenerating token, the Google API refresh token expires 24 hours after it is generated. If the token expires, your connection will fail.
- You can set the refresh token to never expire, but if the token you're currently using has an expiration date, you will need to [regenerate the refresh token](/docs/data/data-cloud-int/guide/c360-a-prepare-your-youtube-connection.md).

## Troubleshooting

Tips for troubleshooting issues that may occur when you ingest a YouTube content into Data 360 using the YouTube connector.
The solutions listed below are unique to the YouTube connector.

### A Data Lake Object and a Data Model Object were created, but the Search Index and Chunking failed

When you create a YouTube connector, you can select the checkbox to automate search indexing. This step is optional, but if you didn’t do it initially, do it now.

#### Issue

Search Index or chunks weren't created.

#### Solution

1. From App Launcher, select **Data Cloud**.
2. Open the **Search Index** tab, select the Search Index you created, and select **Rebuild** from the dropdown menu on the right.
3. Manually create a Search Index from the Search Index tab: **Select New -> Easy Setup**, and select the corresponding DMO.