What is the best practice to follow when calling the SNOWPIPE REST API loadHistoryScan

What is the best practice to follow when calling the SNOWPIPE REST API loadHistoryScan
A . Reading the last 10 minutes of history every 8 minutes
B. Read the last 24 hours of history every minute
C. Read the last 7 days of history every hour

View Answer

Answer: A

Explanation:

This endpoint is rate limited to avoid excessive calls. To help avoid exceeding the rate limit (error code 429), snowflake recommends relying more heavily on insertReport than loadHistoryScan. When calling loadHistoryScan, specify the most narrow time range that includes a set of data loads. For example, reading the last 10 minutes of history every 8 minutes would work well. Trying to read the last 24 hours of history every minute will result in 429 errors indicating a rate limit has been reached. The rate limits are designed to allow each history record to be read a handful of times.