Description

The batched update DAGs have default timeouts that are quite long, mostly because we were unsure how they would shake out once we started running the popularity update regularly:

We could have separate timeout values for the automated and manual batched update runs, but for the time being I think we can safely change the following values:

• UPDATE_TIMEOUT should be set to 30 days (rather than 3 months)
• DAGRUN_TIMEOUT should be set to UPDATE_TIMEOUT + SELECT_TIMEOUT (rather than explicitly setting the timeout)

Additional context

The longest batched_update run we've had was just under 12 days, and that was the automated run for Flickr's popularity update.