ferruzzi commented on issue #19801: URL: https://github.com/apache/airflow/issues/19801#issuecomment-983941612
> So the value was unintended? In that case I guess we could just invent an arbitrary cap to `poke_interval` and just make the DAG error out on parse. It does not need to be that precise either. That would be an easy check in the base sensor, I can get that one done. Should we implement a cap to dag schedule-interval as well? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
