Reviewing Tasks

Overview

This page walks you through how to create, execute, and complete a task with your AI Engineer.

To View a Task

Select AI Data Engineer > Click on your engineer where you wish to view task details.

Task Statuses

A task will progress through multiple stages as it is processed.

• Queued – Task is created and waiting to be picked up by the AI.

• AI Processing – AI Engineer runs code and transformations in draft.

• View Summary – Results with code changes, table updates, and validations.

• Failed – Task errors with logs provided.

• Canceled – Task has been canceled. *Coming Soon*

Task Run Detail

There are several methods to view details about a task.

1. To view the Task detail that was entered for the task, select the Task Status.

2. To view the Task status, select the status icon (e.g. View Summary or Queued )

View Summary Detail

This page breaks out the three main sections visible when reviewing a completed task.

1. View Summary

• Purpose: Provides a high‑level overview of the task execution.

• Contents:

  • Description of the ETL pipeline or transformation implemented.

  • Phases completed and validations performed.

  • Key results (e.g., test pass rate, quality scores).

  • Business rules applied (date handling, price formatting, parsing, etc.).

• Usage: Read first to understand what was achieved and confirm alignment with the task definition.

2. Git Commit Message

• Purpose: Records concise details of changes made in code.

• Contents:

  • Short commit header describing the feature or fix.

  • Bullet‑pointed list of key updates (e.g., ETL implementation, draft‑first processing, validation logic).

• Usage: Helps track code history and link changes back to specific tasks.

3. PR Description

• Purpose: Provides the detailed context for reviewing and merging code.

• Contents:

  • Overview: What the pull request implements.

  • Implementation details: Transformations, rules, or validation logic.

  • Production notes: How safety controls and draft‑first execution are enforced.

• Usage: Review this section before merging to ensure all requirements were met and that production safeguards are intact.

4. Git Folder Access

At the bottom of the Summary View, you can go directly to the Git folder to review the updates.

Outcome: By reviewing these three sections together- Summary, Commit Message, and PR Description-you gain a complete picture of the task’s results, code changes, and readiness for production.