◆ Apache Airflow

Configure S3KeySensor to continue running

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 taskI need to ensure the S3KeySensor for the daily sales report in the 'raw-data' bucket continues…+
I need to ensure the S3KeySensor for the daily sales report in the 'raw-data' bucket continues to run until the 'sales_data_2023-10-27.csv' file arrives, then trigger the processing DAG.
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 I deploy this S3KeySensor, make sure it won't time out if the data is delayed by a few…+
Before I deploy this S3KeySensor, make sure it won't time out if the data is delayed by a few hours, and that it clearly logs when it's waiting and when the file is found, so we don't miss any data loads for the monthly close.
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 S3KeySensor for yesterday's inventory report just timed out again, and the file actually…+
The S3KeySensor for yesterday's inventory report just timed out again, and the file actually arrived an hour later.
The S3KeySensor for yesterday's inventory report just timed out again, and the file actually arrived an hour later. The warehouse team is often late with the upload, and I can't tell them to speed up. I'm afraid this will cause data gaps for the weekly forecast. What's the best way to keep it waiting longer without blocking other critical DAGs?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur S3 sensors frequently time out because upstream systems are unpredictable, causing me to…+
Our S3 sensors frequently time out because upstream systems are unpredictable.
Our S3 sensors frequently time out because upstream systems are unpredictable, causing me to manually restart DAGs and explain data delays. I keep losing time and credibility with the analytics team. What habit should I change to build more resilient data pipelines that can gracefully handle these external delays?
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.