# SPICE ingestion error **URL:** \ **Category:** Q&A\ **Tags:** data-ingestion, spice, error, quick-sight\ **Created:** [July 8, 2022, 9:41am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625 "2022-07-08T09:41:04Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![ArtSal](https://avatars.discourse-cdn.com/v4/letter/a/f475e1/32.png) [@ArtSal](https://community.amazonquick.com/u/ArtSal)\ **Post date:** [July 8, 2022, 9:41am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/1 "2022-07-08T09:41:05Z")
Hi, I am getting this error while trying to ingest a dataset into Spice ‘Error threshold exceeded for dataset (10000) (maxErrors = 10000)’ The dataset has 300k rows and is 9.7 MB. How can i resolve the issue? Best, Artur ---
**Author:** ![Jesse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jesse/32/177_2.png) [@Jesse](https://community.amazonquick.com/u/Jesse)\ **Post date:** [July 8, 2022, 9:09pm UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/2 "2022-07-08T21:09:45Z")
Seems like it is probably related to a data type mismatch, like a field that is coded as a Number but has some characters in it. Or a date field that has dates with different formats in it. ---
**Author:** ![ArtSal](https://avatars.discourse-cdn.com/v4/letter/a/f475e1/32.png) [@ArtSal](https://community.amazonquick.com/u/ArtSal)\ **Post date:** [July 12, 2022, 11:49am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/3 "2022-07-12T11:49:42Z")
Thanks. Will investigate and check my dataset. ---
**Author:** ![WLS-P](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/wls-p/32/36109_2.png) [@WLS-P](https://community.amazonquick.com/u/WLS-P)\ **Post date:** [September 26, 2022, 8:45pm UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/4 "2022-09-26T20:45:11Z")
Hi, @ArtSal. Did @Jesse’s solution work for you? I am marking his reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the Quick Sight Community Q&A Forum! ---
**Author:** ![Fotis\_flex](https://avatars.discourse-cdn.com/v4/letter/f/e47774/32.png) [@Fotis\_flex](https://community.amazonquick.com/u/Fotis_flex)\ **Post date:** [July 11, 2023, 2:57pm UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/5 "2023-07-11T14:57:56Z")
Hi @Jesse , I have the same issue. In the past, I have been refreshing my QS dataset from s3 .csv file. The .csv in s3 was produced by some redshift queries. Now, I changed the redshift definition table so that a specific field is of varchar datatype whereas in the past it was numeric. I also labelled the numeric field to get the varchar values for each row. Now, the .csv file is produced successfully in s3 (with the varhcar values) but QS fails to refresh it and produces this error. Do you have any explanation? To me it is strange that the .csv is not loaded to QS as long as it exitsts in s3 ---
**Author:** ![Jesse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jesse/32/177_2.png) [@Jesse](https://community.amazonquick.com/u/Jesse)\ **Post date:** [July 11, 2023, 5:54pm UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/6 "2023-07-11T17:54:49Z")
Quick Sight datasets store the column type as part of the metadata. If there is a datatype mismatch then the scheduled ingestion likely will fail. You can try to update the field type in your dataset and trigger the ingestion again. Alternatively you can create a new dataset pointing to the same S3 bucket, and then in your analyses you can replace the old one with the new one - that process is usually more forgiving. ---
**Author:** ![Fotis\_flex](https://avatars.discourse-cdn.com/v4/letter/f/e47774/32.png) [@Fotis\_flex](https://community.amazonquick.com/u/Fotis_flex)\ **Post date:** [July 14, 2023, 9:47am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/7 "2023-07-14T09:47:42Z")
Hi @Jesse . Now I create a new .csv file inside an S3 path by copying it there from Redshift. I check that the redshift table exists and all data are there. Same for the .csv in the s3 bucket. But when I try to import it from QS using the manifest directing to my file, the import seems to be successful but no data appear at all! Why?? ---
**Author:** ![Koushik\_Muthanna](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/koushik_muthanna/32/3290_2.png) [@Koushik\_Muthanna](https://community.amazonquick.com/u/Koushik_Muthanna)\ **Post date:** [July 14, 2023, 10:12am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/8 "2023-07-14T10:12:39Z")
@Fotis_flex When the import is successful , can you check how many rows have been imported ? ( post a screenshot ) . ---
**Author:** ![Jesse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/jesse/32/177_2.png) [@Jesse](https://community.amazonquick.com/u/Jesse)\ **Post date:** [July 14, 2023, 3:26pm UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/9 "2023-07-14T15:26:22Z")
Out of curiosity, why aren’t you connecting directly to the Redshift table instead? In your manifest, are you pointing to the bucket or folder? Or are you specifying the file name? I would recommend pointing it to the folder or bucket level. ---
**Author:** ![Fotis\_flex](https://avatars.discourse-cdn.com/v4/letter/f/e47774/32.png) [@Fotis\_flex](https://community.amazonquick.com/u/Fotis_flex)\ **Post date:** [July 20, 2023, 6:26am UTC](https://community.amazonquick.com/t/spice-ingestion-error/4625/10 "2023-07-20T06:26:47Z")
Hallo. That was a good tip! Eveyrithibg now rolls good - thanks!