◆ Apache Airflow

Debug Airflow DAGs for common errors

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 taskDebug the 'product_recommendation_model' DAG for the error that occurred at 2 AM this morning.…+
Debug the 'product_recommendation_model' DAG for the error that occurred at 2 AM this morning. The logs indicate a 'KeyError' in the 'data_transformation' task.
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 acceptWhen debugging the 'product_recommendation_model' DAG's 'KeyError' in 'data_transformation',…+
When debugging the 'product_recommendation_model' DAG's 'KeyError' in 'data_transformation', don't just look at the stack trace. Also, check the upstream 'raw_data_ingestion' task's output for missing columns or malformed data that might have caused the key to be absent. Summarize your findings and suggest a fix.
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 is failing consistently when trying to connect to the external ERP…+
The 'inventory_sync' DAG is failing every time it tries to connect to the external ERP system, but the connection details haven't changed.
The 'inventory_sync' DAG is failing consistently when trying to connect to the external ERP system, but the connection details in our config haven't changed, and I can ping the ERP server directly. The warehouse team is waiting on this data. I'm afraid it's an obscure firewall rule or a certificate issue I can't see. What's the most likely culprit here, and what's the first thing I should check to unblock this?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend an inordinate amount of time manually sifting through verbose logs trying to pinpoint…+
I spend too much time manually sifting through logs to find the actual cause of DAG failures.
I spend an inordinate amount of time manually sifting through verbose logs trying to pinpoint the actual cause of DAG failures, especially for complex DAGs. This is inefficient and delays resolution. What habit can I change in how I approach debugging to more quickly identify the root cause of errors, rather than just reacting to symptoms?
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.