◆ Apache Airflow

Schedule Python scripts in Airflow

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 'daily_inventory_check.py' script to run every morning at 2 AM. It's critical for…+
Schedule the 'daily_inventory_check.py' script to run every morning at 2 AM. It's critical for the warehouse team to have fresh data before their shift starts. Make sure it runs reliably at that time every day.
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 tell the warehouse manager the inventory script is automated, I need to make sure it's…+
Before I tell the warehouse manager the inventory script is automated, I need to make sure it's robust. If the script fails, I need it to retry a couple of times before giving up, and I need to know it will run even if there's a brief network hiccup overnight.
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 warehouse manager is upset because the inventory report is inconsistent. Yesterday it…+
The warehouse manager just complained that yesterday's inventory report was missing, and the one before that was late.
The warehouse manager is upset because the inventory report is inconsistent. Yesterday it didn't run at all, and the day before it was late. I'm afraid I set the schedule incorrectly, or it's silently failing. I don't know if it's a cron issue or a script error. What's the most likely cause for this kind of intermittent failure, and how can I set it up to be absolutely reliable for 2 AM?
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 putting out fires because daily Python scripts are either late, missed, or…+
I keep getting burned by Python scripts that are supposed to run daily but occasionally miss their schedule or fail silently.
I'm constantly putting out fires because daily Python scripts are either late, missed, or failed without me knowing. It's costing us time and trust. What habit should I change to ensure all my scheduled Python scripts run reliably on time, every time, and alert me immediately if they don't?
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.