◆ Apache Airflow

Configure DAG retries

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 taskConfigure the 'product_catalog_update' task to retry up to 3 times with a 5-minute delay…+
Configure the 'product_catalog_update' task to retry up to 3 times with a 5-minute delay between attempts if it fails, so the website always shows the correct product information.
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 acceptFor the 'hourly_web_analytics_processing' pipeline, I need its 'transform_raw_logs' task to…+
For the 'hourly_web_analytics_processing' pipeline, I need its 'transform_raw_logs' task to retry if it fails. It's often due to transient network issues, so set it to retry 5 times with a 2-minute backoff. This will prevent gaps in our hourly dashboards that the marketing team relies on for real-time campaign adjustments.
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 'third_party_api_ingestion' task keeps failing intermittently, causing downstream reports…+
The 'third_party_api_ingestion' task keeps failing intermittently, causing downstream reports to be incomplete.
The 'third_party_api_ingestion' task keeps failing intermittently, causing downstream reports to be incomplete for the sales team. I've set it to retry 3 times, but it still fails. I'm worried if I just increase the retries, it might get stuck in a loop if the API is truly down, but if I don't, we miss critical data. Should I increase retries to 10 with an exponential backoff, or is there a way to add a circuit breaker that stops retrying after a certain number of consecutive failures?
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 getting alerts for failed tasks and then manually restarting them, only for them…+
I spend too much time manually restarting failed tasks that could have recovered on their own.
I'm constantly getting alerts for failed tasks and then manually restarting them, only for them to succeed on the second try. This is a huge time sink and interrupts my focus. What habit should I change to better configure retries for common transient failures, so I only get alerted for actual, persistent problems?
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.