◆ Google Looker

Manage maintenance policies for Looker

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 taskUpdate the maintenance policy for the 'Sales Performance' dashboard to run every Sunday at 2 AM…+
Update the maintenance policy for the 'Sales Performance' dashboard to run every Sunday at 2 AM PST, ensuring the cache clears before new data loads.
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 set the new maintenance schedule for the 'Customer Churn' dashboard, can you suggest a…+
Before I set the new maintenance schedule for the 'Customer Churn' dashboard, can you suggest a policy that balances data freshness with system load, especially considering our peak usage on weekday mornings?
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 Levels' dashboard is showing stale data for the last two days, even though the…+
The 'Inventory Levels' dashboard is showing stale data for the last two days, but the scheduled maintenance ran successfully.
The 'Inventory Levels' dashboard is showing stale data for the last two days, even though the scheduled maintenance policy ran successfully. Priya in operations is furious because she's making critical ordering decisions based on it. I'm worried the underlying data source isn't refreshing, but I can't tell if it's a policy setting or an upstream issue. What's the most likely cause, and how do I diagnose it without disrupting other dashboards?
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 complaints that dashboards are slow right after maintenance, even though I've…+
I keep getting complaints about dashboards being slow immediately after scheduled maintenance.
I keep getting complaints that dashboards are slow right after maintenance, even though I've tried different schedules. It feels like I'm always reacting to performance issues instead of preventing them. What habit should I change to proactively manage maintenance policies so they don't impact user experience?
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 Google Looker'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.