Database: Troubleshooting

Historical extract file not found

If you encounter an error message indicating a StorageFileNotFoundError or a 404 error when fetching historical data, it means an expected historical extract file is missing from storage.

To resolve this issue, you need to reconfigure your fetch. Fetch data once without using the @dt_last_fetch_max placeholder. After a successful fetch, you can re-enable the use of @dt_last_fetch_max.