Learn more in our Data Loads Guide.
1. What does Expired mean?
Expired means that One Model was expecting more files, but they didn’t arrive within the expiry window (the time between the data load opening and getting marked as expired).
Expired is not necessarily a bad thing as it won’t cause a delay in loading or processing, it just means that it didn’t receive all the files it expected to receive. The data source will get marked as Expired only if all data source files marked as required are not received.
The expiry window can be adjusted for each data source, and it is possible to manually expire a data source.
2. What does Waiting mean?
Waiting means they have successfully loaded into Redshift. There is no future status after Waiting today.
E.g. when viewing the File History page, I see files that are still in a “Waiting" status from the previous day. There has been a manual process kicked off today so when will the files in the history ever change from “Waiting”?
3. What does it mean when there are files still showing Waiting but it is under the Processed section?
Waiting means the file has successfully loaded into Redshift and is waiting to be processed.
4. What does Errored mean, and why would this happen?
If a Data Load errors, you will see an Errored status which means that processing failed.
Future data loads will pick up any data that was successfully loaded into Redshift by the erroring data load and were marked as Waiting. Future Data Loads will not try to reload old files into Redshift.
The most common reasons why a file may error are;
- Files not matching the columns/data types expected.
- Wrong file name.
- Invalid columns in file.
- Invalid character types in file.
5. What does Data Processing Cancelled mean? Does that mean the files will be included in the next processing run or will those files just not get processed at all?
Data Processing Cancelled means that the files and their data are in Redshift and Waiting but not yet processed. These files will not be removed or replaced unless someone does so manually or a new Data Load updates the same table. This means that if only one file loaded successfully in a Data Load (and every other file failed), that one table has been updated - and the next Model Processing run will pick it up.