◆ Apache Airflow

Troubleshoot unexpected SIGTERM signals

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 taskCheck the logs for the 'daily_etl_job' for any SIGTERM signals that occurred yesterday,…+
Check the logs for the 'daily_etl_job' for any SIGTERM signals that occurred yesterday, November 14th.
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 acceptMonitor the 'hourly_api_pull' task. If it receives a SIGTERM signal, immediately trigger a…+
Monitor the 'hourly_api_pull' task. If it receives a SIGTERM signal, immediately trigger a retry with a 5-minute delay and notify the on-call engineer, Sarah, via Slack, including the exact timestamp of the signal.
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 'monthly_report_generation' task keeps getting SIGTERM'd after about 30 minutes, but it…+
The 'monthly_report_generation' task keeps getting SIGTERM'd after about 30 minutes, but it completes successfully if I manually restart it.
The 'monthly_report_generation' task keeps getting SIGTERM'd after about 30 minutes, but it completes successfully if I manually restart it. I'm afraid it's hitting a memory limit, but it could also be a timeout from the external API it's calling. The finance team needs this report by Monday morning. What's the most likely cause for the SIGTERM, and how can I confirm it quickly?
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 chasing down unexpected SIGTERM signals in long-running data processing tasks,…+
I'm constantly chasing down unexpected SIGTERM signals in long-running data processing tasks.
I'm constantly chasing down unexpected SIGTERM signals in long-running data processing tasks, which often indicates resource exhaustion or external process killers. This eats into my time and delays critical data delivery. What habit should I change in how I design or monitor these tasks to proactively identify and prevent these signals before they cause failures?
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.