◆ Apache Airflow

Schedule tasks daily

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
See the prompt↓All Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSchedule the 'daily_sales_report' DAG to run every day at 6 AM Pacific Time, starting tomorrow,…+
Schedule the 'daily_sales_report' DAG to run every day at 6 AM Pacific Time, starting tomorrow, June 20th.
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 acceptBefore I schedule the 'inventory_snapshot' DAG, I need to make sure it gracefully handles…+
Before I schedule the 'inventory_snapshot' DAG, I need to make sure it gracefully handles missing data from the upstream ERP system, which sometimes has delays. If the source data isn't ready by 2 AM, it should wait an hour and retry, up to three times, before alerting the data ops team.
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 'customer_segmentation' DAG failed last night because the upstream marketing data wasn't…+
The 'customer_segmentation' DAG failed last night because the upstream marketing data wasn't ready, but it still ran, producing empty segments.
The 'customer_segmentation' DAG failed last night because the upstream marketing data wasn't ready, but it still ran, producing empty segments. The marketing team is furious because their campaigns went out to the wrong groups. I'm afraid to add a hard dependency that might block it indefinitely if their system is down, but I can't have bad data going out. What's the best way to ensure data readiness without creating a new single point of failure, and how do I explain this to the marketing director by end of day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent calls because scheduled DAGs run with stale or incomplete…+
I keep getting pulled into urgent calls because scheduled DAGs run with stale or incomplete upstream data.
I keep getting pulled into urgent calls because scheduled DAGs run with stale or incomplete upstream data, causing downstream reports to be wrong. I spend too much time manually checking data freshness before each run. What habit should I change to reliably ensure data quality for scheduled tasks without adding excessive manual overhead or creating brittle dependencies?
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.