Analysis / Data engineering and quality
Track analytical workload by query category
Summarize analytical query frequency, duration and recorded resource use, then identify reusable Models and scheduling options for review.
Data analyst · Analytics engineer
Bring this question into Chat
Your starting prompt.
Use [query history] to summarize analytical workload by [query category], duration, frequency and execution window. Include engine cost or resource counters only where recorded. Identify repeated workloads, peak contention and candidates for reusable Models or adjusted schedules. Produce a workload review with actual measured units, and label any cost scenarios as estimates rather than substituting runtime for billed spend.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Profile keys, row counts, types, missing values and join cardinality. Retain source lineage and concrete exception records so a correction can be checked.
For this task, check
Runtime is not a reliable measure of cost without engine specific billing or resource counters.
This starting prompt has no published worked example yet. Begin with a small sample and check the calculations before relying on the result.
Before you begin
- Bring exports you are allowed to upload, or data your Workspace can already query.
- Choose the reporting period and agree what each record represents.
Work with permitted files or queryable data. Verify the result against the original records.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.