◆ Apache Airflow

Schedule a DAG to run every 5 minutes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSchedule the `sensor_data_ingestion` DAG to run every 5 minutes, starting immediately, so we…+
Schedule the `sensor_data_ingestion` DAG to run every 5 minutes, starting immediately, so we capture real-time updates.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptOur real-time analytics dashboard needs the `web_traffic_update` DAG to run every 5 minutes…+
Our real-time analytics dashboard needs the `web_traffic_update` DAG to run every 5 minutes during business hours (9 AM - 5 PM PST) on weekdays, but only once an hour overnight and on weekends. We need to balance fresh data with not overloading the system.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe inventory sync DAG ran at 2 AM instead of 3 AM last night, causing a brief discrepancy in…+
The `inventory_sync` DAG ran at 2 AM instead of 3 AM, causing a brief discrepancy in the online store's stock levels.
The inventory sync DAG ran at 2 AM instead of 3 AM last night, causing a brief discrepancy in the online store's stock levels. I'm afraid of more unexpected runs affecting our customer experience. What's the most robust way to ensure a DAG consistently runs at a precise time, accounting for time zones, and how can I quickly verify the next scheduled run to prevent another incident?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly dealing with DAGs running at unexpected times or missing their schedules,…+
I frequently encounter issues where DAGs run at unexpected times or miss their schedules, leading to data staleness or system overload.
I'm constantly dealing with DAGs running at unexpected times or missing their schedules, leading to data staleness or system overload. This reactive firefighting to adjust schedules is a huge time sink. What habit can I change to proactively manage and verify our DAG schedules, so I can trust our data pipelines to run precisely when needed?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Airflow's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.