<p dir="auto">Make it possible to create a Trigger config template, and make it possible to enforce the configuration.</p>
<p dir="auto"><strong>Use case / motivation</strong></p>
<p dir="auto">The use case would be to make ETL Batch jobs configurable, for the use case: Of getting data from a specific time, a DAG that depends on a givin input. like a list of ID's a email, So an extraction from a db can be taken out of Airflow and the result are getting send per mail.</p>
<p dir="auto"><strong>Are you willing to submit a PR?</strong></p>
<p dir="auto">No</p>
<p dir="auto"><strong>Related Issues</strong></p>
<p dir="auto">Didn't find anything that follows the idea.</p>
<p dir="auto"><strong>Description</strong></p>
<p dir="auto">A task run by the LocalTaskJob periodically updates a timestamp to indicate that the task is still alive and running. If the task is unable to update this timestamp for a long time (for example, due to DB connection errors), the scheduler may reschedule the task to run again. In such a case, it's possible that two instances of the task are running. The task can monitor the time since last heartbeat and kill itself to prevent such cases.</p>
<p dir="auto"><strong>Use case / motivation</strong></p>
<p dir="auto"><strong>Related Issues</strong></p>
<p dir="auto">Moved here from <a href="https://issues.apache.org/jira/browse/AIRFLOW-374" rel="nofollow">https://issues.apache.org/jira/browse/AIRFLOW-374</a></p>