◆ Apache Airflow

Migrate from Airflow 2 to Airflow 3

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 taskMigrate the 'daily_sales_report' workflow from the older orchestration environment to the new…+
Migrate the 'daily_sales_report' workflow from the older orchestration environment to the new cluster. Verify all connections and variables are correctly transferred and the workflow runs successfully by Tuesday morning.
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 we migrate the core data warehouse workflows to the new orchestration platform, analyze…+
Before we migrate the core data warehouse workflows to the new orchestration platform, analyze the existing workflows for any deprecated operators or syntax that might break. Provide a report of necessary changes and an estimated effort for each, so we can plan the migration efficiently and avoid last-minute surprises.
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' workflow failed immediately after migrating to the new…+
The 'customer_segmentation' DAG failed after migration to Airflow 3, but it worked perfectly in Airflow 2.
The 'customer_segmentation' workflow failed immediately after migrating to the new orchestration platform, even though it passed all pre-migration tests and ran fine in the old environment. The marketing team needs these segments by end of day for a campaign. I'm afraid this is a deeper compatibility issue I missed. What's the most likely cause for a workflow failing post-migration despite passing tests, and what's the fastest way to get it running again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach time we upgrade our data orchestration platform, it feels like we're just reacting to…+
Every Airflow version upgrade introduces unexpected breaking changes and takes longer than planned.
Each time we upgrade our data orchestration platform, it feels like we're just reacting to broken workflows and unexpected compatibility issues, causing project delays and late nights. This reactive approach is burning us out. What habit should I change in our upgrade planning and execution to anticipate these problems better and make future migrations smoother and more predictable?
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.