Action / Business automation and AI evaluation
Prepare a dependency-aware Model refresh Action
Prepare a Model refresh Action in Proforma using existing lineage and refresh helpers. Review upstream readiness and freshness checks before scheduling.
Analytics engineer
Bring this question into Chat
Your starting prompt.
Inspect [target Model] and its current lineage in [database], then draft a dependency-aware refresh Action. Use existing Model planning and refresh helpers, identify inaccessible upstreams and record actual refresh outcomes rather than assuming success. Propose [cadence and timezone] and a freshness check after refresh. Keep the Action unscheduled until release review. Do not create a separate pipeline entity or claim unavailable dependencies were refreshed.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Define inputs, outputs, permissions and failure conditions before implementing an Action. Evaluate AI against representative labeled examples and retain human approval for consequential steps.
For this task, check
The data owner should confirm refresh order, upstream access and the freshness definition before release.
Before you begin
- Permitted Models and explicit database access
- Configured Action runtime
- Approved deployment before scheduling
Repeat execution requires a configured Action. Agree the scope and authority before any external changes or messages.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Proposed dependency inspection in the revenue database; customer Source access is missing. No refresh has run.
These invented records explain the method. They are not a recorded Proforma run.
| Object | Type | Upstream | Permission |
|---|---|---|---|
| orders | Source | Configured ingest | Read allowed |
| daily_revenue | Table Model | orders | Refresh allowed |
| customers | Source | Configured ingest | Unavailable |
| weekly_accounts | Table Model | daily_revenue; customers | Refresh allowed |
| Plan step | Object | Proposed state | Evidence needed |
|---|---|---|---|
| 1 | orders | Inspect freshness | Actual load timestamp |
| 2 | daily_revenue | Could refresh after Source check | Actual refresh result |
| 3 | customers | Blocked by access | Owner-approved permission |
| 4 | weekly_accounts | Blocked by upstream | All inputs accessible and fresh |
Method
Use existing Model lineage and refresh planning helpers with an explicit database. Check permitted Sources, then upstream table Models before the target. A plan row is not a refresh receipt or evidence of success.
What the result tells you
Target permission alone does not satisfy its upstream requirements. This proposed Action is unscheduled; release approval, actual access and observed outcomes are needed before claiming a refresh.
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.