◆ Apache Airflow

Troubleshoot slow scheduler performance

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 taskThe scheduler is running really slow and it's holding up all the new data loads. Can you check…+
The scheduler is running really slow and it's holding up all the new data loads. Can you check the logs for the last hour and tell me what's eating up all the resources so we can get this moving again?
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 acceptThe scheduler performance has been inconsistent this week, causing delays in our reporting.…+
The scheduler performance has been inconsistent this week, causing delays in our reporting. Before it impacts the Monday morning dashboards, let's identify the top 3 biggest bottlenecks in the last 24 hours and propose a quick fix for each, focusing on anything that could be easily tuned.
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 Friday morning sales report just missed its SLA again because the scheduler was crawling.…+
Our critical Friday morning sales report just missed its SLA because the scheduler was crawling.
The Friday morning sales report just missed its SLA again because the scheduler was crawling. The team is blaming the new DAGs, but I suspect it's something else, maybe a database connection or too many zombie tasks. I can't tell them I don't know why it failed, but I also can't just point fingers. What's the most likely culprit for this kind of intermittent, severe slowdown, and what's the first thing I should check to get a definitive answer before the VP starts asking questions?
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 scheduler performance issues that delay critical reports,…+
I keep getting pulled into urgent scheduler performance issues that delay critical reports.
I keep getting pulled into urgent scheduler performance issues that delay critical reports, often after hours. It feels like we're always reacting. What habit should I change to proactively monitor scheduler health and identify potential bottlenecks before they impact our business users and cause these fire drills?
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.