11.3 Debugging Tools

Taibles provides powerful tools to help you debug and fix issues in your automations. This section shows you each tool, when to use it, and how to access it through the interface.

Overview of Available Tools

Your Debugging Toolkit

Manual Re-run

Retry failed cells
Test configuration changes
Process new data

Clear and Reset

Start fresh after changes
Remove incorrect data
Reset failed states

Real-Time Monitoring

Watch execution live
Visual state indicators
Column status summaries

Filtering

Focus on problems
Show only failed cells
Hide working rows

Test Strategy

Sample row testing
Incremental validation
Safe rollout

Tool 1: Manual Re-run

What It Does

Re-executes cells with current configuration

Use when:

Fixing failures (retry after fix)
Testing changes (verify new config works)
Filling gaps (process new rows)
Refreshing data (re-enrich stale data)

Access Methods

Column Header Menu - Re-run Options

Access re-run modes from the column menu

company_dataCalculated

How to access:

Click the three-dot menu (⋮) in the column header
Hover over "Re-run" to see submenu
Select the appropriate re-run mode

Method A: Column Header Menu

Click the three-dot menu (⋮) in the column header
Select "Re-run" to see options
Choose mode:
- "Re-run empty cells": Only cells that have no data yet
- "Re-run failed cells": Only cells that failed (retry after fix)
- "Re-run all cells": Every cell regardless of state

Row Selection - Context Menu

Re-run specific rows using right-click menu

3 rows selected

How to use:

Select rows using checkboxes
Right-click on selected rows
Choose "Recalculate cells"
Select which column(s) to re-run

Method B: Context Menu (Row Selection)

Select rows using checkboxes
- Click checkbox on specific rows
- Or select all visible with header checkbox
Right-click selected rows
Choose "Recalculate cells" from context menu
Select column(s) to re-run
Cells execute for selected rows only

Re-run Modes Explained

Re-run Modes Comparison

Choose the right mode for your situation

Mode 1: Re-run Empty Cells

Fill Gaps

When to use:

New rows added, need to fill in the gaps

What it processes:

Only cells showing Ready (empty)

Efficient: Skips all completed cells, saves API costs

Mode 2: Re-run Failed Cells

Retry

When to use:

After fixing configuration or when API is back online

What it processes:

Only cells showing Unsuccessful (failed)

Smart: Leaves successful cells alone, only retries failures

Mode 3: Re-run All Cells

Recalculate All

When to use:

Configuration changed significantly, need fresh calculations

What it processes:

ALL cells regardless of current state

Caution: Expensive! Recalculates everything. Test on samples first.

Quick Comparison

Mode	Processes	Cost	Use Case
Empty	Only empty cells	Low	New rows added
Failed	Only failed cells	Medium	After fixing errors
All	Every cell	High	Config changed

Mode 1: Re-run Empty Cells

When to use: Fill in gaps after adding new rows

What it does:

Only processes cells that are empty (showing "Ready")
Skips cells that already have data
Efficient for filling new rows without reprocessing existing

Example scenario:

Before:
- Row 1-100: Completed ✓
- Row 101-110: Ready (newly added)

After "Re-run empty cells":
- Row 1-100: Completed ✓ (unchanged)
- Row 101-110: Queued → Running → Completed ✓

UI interaction:

Column menu (⋮) → "Re-run" → "Re-run empty cells"
Confirmation: "All empty cells in this column will be calculated."
Click "Recalculate"
Only empty cells execute

Mode 2: Re-run Failed Cells

When to use: Retry after fixing configuration or temporary failures

What it does:

Only processes cells showing "Error" or "Unsuccessful"
Skips successful cells
Perfect for retry after fixing errors

Example scenario:

Before:
- Row 1-90: Completed ✓
- Row 91-100: Unsuccessful ✗ (API was down)

[API service recovers]

After "Re-run failed cells":
- Row 1-90: Completed ✓ (unchanged)
- Row 91-100: Queued → Running → Completed ✓

UI interaction:

Column menu (⋮) → "Re-run" → "Re-run failed cells"
Confirmation: "All failed cells in this column will be re-tried."
Click "Recalculate"
Only failed cells execute

Efficiency: Saves time and API costs by not reprocessing successful cells

Mode 3: Re-run All Cells

When to use: Configuration changed, need to recalculate everything

What it does:

Processes ALL cells regardless of current state
Overwrites existing data with fresh calculation
Use after significant configuration changes

Example scenario:

You changed:
- AI prompt in column
- API service (switched from one provider to another)
- Logic in custom code

Need to recalculate all rows with new config

After "Re-run all cells":
- All cells: Queued → Running → Completed ✓
- All data refreshed with new configuration

UI interaction:

Column menu (⋮) → "Re-run" → "Re-run all cells"
Confirmation: "All values in this column will be re-calculated."
Warning if dependencies: Shows downstream columns that may also recalculate
Click "Recalculate"
All cells execute

Caution:

Can be expensive (many API calls)
Triggers downstream dependencies if configured
Consider testing on sample first

Confirmation Dialogs

Standard Confirmation

Simple re-run confirmation

Recalculate Column?

All failed cells in this column will be re-tried.

Do you want to proceed?

With Dependencies

Shows downstream impact

Recalculate Column?

This column has the following downstream dependencies:

lead_score send_email

Re-calculation of cells in this column may trigger a re-calculation of the dependent columns.

Do you want to proceed?

Before re-running, Taibles shows confirmation to help you understand the impact.

Standard confirmation:

Shows what will be recalculated
Asks you to confirm before proceeding

With downstream dependencies:

Lists columns that depend on this one
Warns that re-calculation may trigger dependent columns
Helps you understand full impact

Purpose: Helps you understand impact before executing

Monitoring Re-run Progress

Real-Time Column Progress

Column header shows live execution status

company_data

Execution Timeline

Start:🕐 Queued: 1000

After 1m:⟳ Running: 50🕐 Queued: 850✓ Done: 100

After 5m:⟳ Running: 20🕐 Queued: 200✓ Done: 780

After 10m:✓ Done: 1000

Click status to navigate

Click "Running" or "Queued" to jump to the active cell

Column header updates in real-time:

During execution:

company_data
────────────
⟳ Running: 1
🕐 Queued: 45

Spinning loader icon: Currently processing
Clock icon: Waiting in queue

Click status to navigate to first running/queued cell

Cell State Indicators

Visual feedback for each cell's execution state

Ready (Empty)Ready

Not processed yet, waiting to execute

Queued Queued

Waiting in queue, will execute soon

Running Running

Currently executing, in progress

Completed Completed

Successfully executed with result

Unsuccessful Unsuccessful

Execution failed, click to see error details

Skipped Skipped

Condition not met or dependencies missing

Rate Limited Rate Limited

Throttled by rate limit, will execute when available

Scheduled Scheduled

Waiting for scheduled time to execute

Interaction Tips

Hover over any cell to see quick preview
Click a cell to open detailed sidebar view
Failed cells show error button to view details

Individual cells update:

Queued: Blue badge with clock icon, "Queued"
Running: Blue badge with spinning gear, "Running"
Completed: Green badge with checkmark, "Completed"
Unsuccessful: Red badge with lightning bolt, "Unsuccessful"

Tool 2: Clear and Reset

What It Does

Resets cells to empty state and deletes data

Use when:

Configuration changed significantly
Want fresh start with new settings
Need to remove incorrect data
Testing different approaches

Access Method

Clear Menu - Reset Cell Data

Access clear options from column menu

enrichment_data

Clear

✓ Column stays in taible
✓ Configuration preserved
✓ Cells reset to empty
✓ Can re-run later

Delete

✗ Column removed entirely
✗ Configuration lost
✗ Data deleted permanently
✗ Cannot undo

Column Header Menu:

Click three-dot menu (⋮) in column header
Select "Clear" to see options
Choose scope:
- "Clear column": All cells in column
- "Clear cell range": Selected rows only (if rows selected)

Clear Operation Details

Clear Operation - What Happens

Understanding the clear process

Before Clear

enrichment_data

Completed

{"company": "Acme"}

Unsuccessful

Error: API timeout

Completed

{"company": "TechCo"}

After Clear

enrichment_data

Ready

Empty

Ready

Empty

Ready

Empty

What Changes During Clear

Cell State

All cells → Ready

Cell Data

Deleted (set to empty)

Error Info

Cleared (if was failed)

Configuration

Preserved (unchanged)

Downstream Effects

If other columns depend on this column, they may also recalculate based on their configuration. The system handles this automatically.

What happens when you clear:

1. Cell state → Ready (gray, empty)

2. Cell data → deleted

3. Error info → cleared (if was failed)

4. Downstream effects:

Downstream columns may recalculate based on their configuration
System automatically handles dependent columns

Clear Confirmation Dialog

System asks for confirmation before clearing

Clear all values in "company_data"?

This will:

Set all cells to empty (Ready)
Delete stored results
Clear any error information
Downstream dependencies may recalculate

Proceed with clearing this column?

The system shows a clear confirmation with:

What will be cleared
Impact on data
Warning about downstream effects
Options to cancel or proceed

Clear Workflow Example

Scenario: Changed API provider in column, need fresh data

Steps:

Update column configuration:
- Column header gear icon (⚙️)
- Change from one provider to another
- Save
Clear existing data:
- Column menu (⋮) → "Clear" → "Clear column"
- Confirm
- All cells → Ready
Re-run with new config:
- Column menu (⋮) → "Re-run" → "Re-run empty cells"
- All cells execute with new API provider

Result: Fresh data from new source

Clear vs. Delete Column

Important distinction:

Clear (keeps column, removes data):

Column stays in taible
Configuration preserved
Cells reset to empty
Can re-run to get fresh data

Delete (removes column entirely):

Column removed from taible
Configuration lost
Data deleted permanently
Cannot undo

Use clear when: Testing different configurations

Use delete when: Column no longer needed

Tool 3: Cancel Running Tasks

What It Does

Stops execution of currently running or queued cells

Use when:

Realized configuration is wrong
Want to stop expensive operations
Need to make changes before continuing

Access Method

Cancel Menu - Stop Running Tasks

Stop queued or running cells

enrichment_data

Queued: 45

When to cancel:

Realized configuration is wrong
Want to stop expensive operations
Need to make changes before continuing

Column Header Menu:

Click three-dot menu (⋮) in column header
Select "Cancel" to see options
Choose scope:
- "Cancel all tasks": Stop all queued/running cells
- "Cancel task range": Stop selected rows only (if rows selected)

Cancel Behavior

Cancel Behavior - What Happens

Understanding what cancel does to different cell states

Queued Cells

Queued Waiting in queue

ReadyRemoved from queue, never started

Running Cells

Running Currently executing

ReadyStopped mid-execution, partial results discarded

Completed Cells

Completed Already done

Completed Unchanged, keeps data

After canceling:

You can fix your configuration and re-run the cells safely. Cancel doesn't delete completed data, so successful cells remain untouched.

What happens:

Queued cells → Ready (removed from queue, never started)

Running cells → Ready (stopped mid-execution, partial results discarded)

Completed cells → Unchanged (keep their data)

Result: Can now fix configuration and re-run

Tool 4: Real-Time Monitoring

What It Provides

Visual feedback on execution state and progress

Components:

Cell state indicators
Column header summaries
Live updates

Cell State Indicators

Cell State Visual Reference

Complete guide to cell state indicators

State	Badge	Color	Icon	Meaning
Ready	Ready	Gray	None	Not processed yet
Queued	Queued	Blue	Clock	Waiting in queue
Running	Running	Blue	Spinning gear	Currently executing
Completed	Completed	Green	Checkmark	Successful
Unsuccessful	Unsuccessful	Red	Lightning bolt	Error occurred
Skipped	Skipped	Gray	Slash icon	Condition not met
Rate Limited	Rate Limited	Yellow	Pause	Throttled by limit

Visual elements in each cell:

State	Badge	Color	Icon	Meaning
Ready	"Ready"	Gray	None	Not processed yet
Queued	"Queued"	Blue	Clock	Waiting in queue
Running	"Running"	Blue	Spinning gear	Currently executing
Completed	"Completed"	Green	Checkmark	Successful
Unsuccessful	"Unsuccessful"	Red	Lightning bolt	Error occurred
Skipped	"Skipped"	Gray	Icon	Condition not met
Rate Limited	"Rate Limited"	Yellow	Pause	Throttled by limit

Hover over cell: See quick preview

Click cell: Open sidebar with full data or error details

Column Header Summaries

Column Header Status Summaries

Real-time execution counts at a glance

company_data

Click to navigate to running cell

company_data

Click to navigate to first queued cell

company_data

Click to navigate to first failed cell

Interactive Navigation

Click any status indicator to jump directly to the relevant cell. This helps you quickly find and inspect cells that need attention.

Column header shows:

Running count:

company_data
────────────
⟳ Running: 1

Spinning loader icon
Number currently executing
Click to navigate to running cell

Queued count:

company_data
────────────
🕐 Queued: 45

Clock icon
Number waiting in queue
Click to navigate to first queued cell

Failed count:

company_data
────────────
❌ Failed: 5

Error indicator
Number in failed state
Click to navigate to first failed cell

Real-Time Updates

Real-Time Updates - Live Progress

Watch execution happen live without refreshing

See progress in real-time

Watch cells change state as they execute

Catch failures immediately

See errors as they happen, not after all complete

Monitor bulk operations

Track progress on thousands of cells

Multi-user awareness

See changes from other team members

Example: Running 1,000 Cells

Start:

🕐 Queued: 1000

After 1m:

⟳ Running: 50🕐 Queued: 850✓ Done: 100

After 5m:

⟳ Running: 20🕐 Queued: 200✓ Done: 780

After 10m:

✓ Done: 1000

No Page Refresh Needed

All updates happen automatically through live connections. You can watch the progress happen in real-time without any manual refreshing!

Live updates:

What updates automatically:

Cell states change (Ready → Queued → Running → Completed)
Column header counts adjust
Visual indicators refresh
No page refresh needed

Benefits:

See progress in real-time
Catch failures immediately
Monitor bulk operations
Multi-user awareness (see other users' changes)

Example: Run 1,000 cells

Start:    🕐 Queued: 1000
After 1m: ⟳ Running: 50, 🕐 Queued: 850, ✓ Done: 100
After 5m: ⟳ Running: 20, 🕐 Queued: 200, ✓ Done: 780
After 10m: ✓ Done: 1000

Watch it happen live without refreshing!

Tool 5: Filtering for Debugging

What It Does

Shows only relevant rows to focus on problems

Use when:

Many rows, few failures
Want to see only errors
Review specific states
Verify specific data

How to Filter by State

Filter Modal - Focus on Problems

Show only rows that match specific conditions

Configure Filters

Configure filters to show only rows that match specific conditions

Filter 1

Value

State values you can filter by:

Ready - Empty cells

Queued - Waiting

Running - Processing

Completed - Successful

Unsuccessful - Failed

Skipped - Not met

Rate Limited - Throttled

Scheduled - Waiting

Step 1: Open Filter Modal

Click "Filter" button in taible header
- Top action bar
- Funnel icon
Filter modal opens

Step 2: Add Filter

Click "+ Add Filter" button
Configure filter:
- Field: Select column
- Operator: "Equals"
- Value: Type state name
State values you can filter by:
- Ready (empty cells)
- Queued (waiting)
- Running (processing)
- Completed (successful)
- Unsuccessful (failed)
- Skipped (condition not met)
- Rate Limited (throttled)
- Scheduled (waiting for schedule)
Click "Apply Filters"

Step 3: View Filtered Results

Filtered Results - Focus on Failures

Shows only matching rows

Before Filter1,000 rows

company_name

enrichment_column

Acme Corp

Completed

TechStart

Unsuccessful

Global Inc

Completed

+ 997 more rows...

Filter: enrichment_column = "Unsuccessful"

After Filter12 rows

company_name

enrichment_column

TechStart

Unsuccessful

DataSys LLC

Unsuccessful

CloudTech

Unsuccessful

+ 9 more failed rows...

Now you can focus exclusively on problems!

From 1,000 rows down to just 12 failures. You can now investigate and fix these specific issues without distraction.

Grid now shows only matching rows

Example: Show only failures

Filter: enrichment_column equals "Unsuccessful"
Result: 12 rows (out of 1,000)

Now you can focus exclusively on problems!

Common Debugging Filters

Quick reference for common filter patterns

Show Only Failures

Field: [column_name]

Operator: Equals

Value: Unsuccessful

Show Unprocessed

Field: [column_name]

Operator: Equals

Value: Ready

Show Rate Limited

Field: [column_name]

Operator: Equals

Value: Rate Limited

Show Successful

Field: [column_name]

Operator: Equals

Value: Completed

Combine Multiple Filters

Example: Failed High-Value Leads

Filter 1: score_lead equals "Unsuccessful"

AND

Filter 2: lead_score greater than 70

Result: Only failed cells for qualified leads (score > 70)

Show only failures:

Field: [column_name]
Operator: Equals
Value: Unsuccessful

Show unprocessed:

Field: [column_name]
Operator: Equals
Value: Ready

Show rate-limited:

Field: [column_name]
Operator: Equals
Value: Rate Limited

Show successful:

Field: [column_name]
Operator: Equals
Value: Completed

Combine filters (multiple conditions):

Filter 1: score_lead equals "Unsuccessful"
AND
Filter 2: lead_score greater than 70

Result: Only failed cells for qualified leads

Clearing Filters

To return to full view:

Click "Filter" button again
Click "Clear All Filters" or remove individual filters
Grid shows all rows again

Tool 6: Test Strategy (Sample Row Testing)

What It Is

Systematic approach to test changes safely

Concept: Test on few rows before processing all

Benefits:

Catch errors early
Save API costs
Faster iteration
Confident rollout

The Testing Workflow

Sample Testing Workflow

Safe, systematic approach to testing changes

Make Configuration Change

Edit column settings
Update prompt, API, logic, etc.
Save configuration

Select Test Rows

Choose 3-5 representative rows:

Mix of different scenarios
Include edge cases
Typical data + unusual data

💡 Pro tip: Usually rows 1-5 work well for testing

Run on Test Sample

Right-click selected rows
Choose "Recalculate cells"
Select column to test
Watch execution:
- ✓ Cells turn green (Completed)?
- ✗ Or red (Unsuccessful)?

Verify Results

For each test cell:

Click cell to inspect
Check data looks correct
Verify logic worked as expected

If test succeeds: Configuration is good ✓

If test fails: Debug, fix, retry

Run on All Rows

Once test sample succeeds:

Clear selection (uncheck test rows)
Open column menu (⋮)
Choose "Re-run" mode:
- "Re-run empty cells" if others untouched
- "Re-run all cells" if need full recalc
Monitor progress
All rows process with verified config ✓

Benefits of Sample Testing:

Catch errors early - Find problems with 5 tests, not 10,000
Save API costs - Avoid wasting credits on wrong config
Faster iteration - Quick feedback loop for changes
Confident rollout - Know it works before full run

Step 1: Make Configuration Change

Edit column settings
Update prompt, API, logic, etc.
Save configuration

Step 2: Select Test Rows

Choose 3-5 representative rows:

Mix of different scenarios
Include edge cases
Typical data + unusual data

Select rows:

Click checkboxes on test rows
Usually rows 1-5 work well

Step 3: Run on Test Sample

Right-click selected rows
Choose "Recalculate cells"
Select column to test
Watch execution:
- Do cells turn green (Completed)? ✓
- Or red (Unsuccessful)? ✗

Step 4: Verify Results

For each test cell:

Click cell
Check data looks correct
Verify logic worked as expected

If test succeeds: Configuration is good ✓

If test fails: Debug, fix, retry

Step 5: Run on All Rows

Once test sample succeeds:

Clear selection (uncheck test rows)
Column menu (⋮)
Re-run → Choose appropriate mode:
- "Re-run empty cells" if others untouched
- "Re-run all cells" if need to recalculate all
Monitor progress
All rows process with verified configuration

Example: Testing Prompt Change

Testing Example: AI Prompt Change

Real-world example of safe testing workflow

Scenario

Updating AI prompt in lead scoring column for 10,000 rows

Step 1: Select 5 Test Leads

company_name

Type

score_lead

Enterprise Corp

Obviously Qualified

Ready

Global Solutions

Obviously Qualified

Ready

Small Startup

Obviously Unqualified

Ready

Local Shop

Obviously Unqualified

Ready

MidSize Inc

Borderline Case

Ready

Step 2: Verify Test Results

company_name

Expected

Score

Result

Enterprise Corp

High score (>80)

Global Solutions

High score (>80)

Small Startup

Low score (<30)

Local Shop

Low score (<30)

MidSize Inc

Mid score (50-60)

Time Saved

Testing on 5 rows:5 minutes

If config was wrong, reprocessing 10,000:30+ minutes wasted

Results look good → Safe to run on all 10,000 rows ✓

Scenario: Updating AI prompt in lead scoring column

Test workflow:

Change prompt in column configuration
Select 5 test leads:
- 2 obviously qualified
- 2 obviously unqualified
- 1 borderline case
Right-click → "Recalculate cells" → Select scoring column
Verify scores:
- Row 1 (qualified): Score = 85 ✓
- Row 2 (qualified): Score = 92 ✓
- Row 3 (unqualified): Score = 15 ✓
- Row 4 (unqualified): Score = 22 ✓
- Row 5 (borderline): Score = 55 ✓
Results look good → Run on all 10,000 rows

Time saved: 5 minutes testing vs. 30 minutes reprocessing all if config was wrong

Debugging Tools Quick Reference

Tool	When to Use	How to Access	Result
Re-run empty	Fill new rows	Column menu → Re-run	Processes only empty cells
Re-run failed	Retry after fix	Column menu → Re-run	Processes only failed cells
Re-run all	Config changed	Column menu → Re-run	Processes all cells
Clear column	Fresh start	Column menu → Clear	Resets all to empty
Cancel tasks	Stop execution	Column menu → Cancel	Stops queued/running cells
Filter by state	Focus on issues	Filter button → Add filter	Shows only matching rows
Sample testing	Safe changes	Select rows → Recalculate	Tests on subset first
Real-time monitor	Watch progress	Automatic	Live state updates

Best Practices for Using Debugging Tools

Practice 1: Always Test on Samples First

DON'T

Change configuration
Re-run all 10,000 rows immediately
Discover error after 1,000 API calls

Result: Wasted time, API costs, and need to fix and retry everything

DO

Change configuration
Test on 5 rows
Verify works
Then run on all

Result: Safe, confident, cost-effective rollout

Don't:

1. Change configuration
2. Re-run all 10,000 rows immediately
3. Discover error after 1,000 API calls

Do:

1. Change configuration
2. Test on 5 rows
3. Verify works
4. Then run on all

Practice 2: Use Appropriate Re-run Mode

Match mode to situation:

New rows added → Re-run empty cells
Fixed configuration → Re-run failed cells
Significant change → Re-run all cells

Don't always use "Re-run all" (wastes API calls)

Practice 3: Filter Before Bulk Operations

Best Practice: Filter Before Bulk Operations

Prevent accidental operations on wrong rows

Filter

Show only relevant rows

Verify

Check this is what you want to process

Select All

Select all (filtered view only)

Execute

Run operation on selected

Clear Filter

Return to full view when done

Prevents Mistakes

By filtering first, you ensure you're only operating on the rows you intend to modify. This prevents accidentally clearing or recalculating the wrong data.

Workflow:

Filter to show only relevant rows
Verify this is what you want to process
Select all (filtered view)
Execute operation
Clear filter when done

Prevents accidentally processing wrong rows

Practice 4: Monitor Real-Time, Act Fast

Best Practice: Monitor Real-Time, Act Fast

Don't wait for all cells to fail before investigating

Watch Column Headers During Execution

If you see many failures appearing:

Cancel remaining tasks

Column menu (⋮) → Cancel → Cancel all tasks

Check first few failures

Look for patterns in error messages

Fix configuration

Update column settings based on error pattern

Resume with re-run failed

Column menu (⋮) → Re-run → Re-run failed cells

Don't Wait!

Bad: Let all 10,000 cells fail before investigating

Good: See 10 failures, cancel immediately, investigate and fix

Fast Response = Lower Cost

By catching failures early and canceling quickly, you save API costs and can fix issues faster. The real-time monitoring is there to help you act quickly!

Watch column headers during execution:

If see many failures:

Cancel remaining tasks (Column menu → Cancel)
Check first few failures for pattern
Fix configuration
Resume with re-run failed

Don't wait for all 10,000 to fail before investigating!

Practice 5: Use Clear Sparingly

Clear is destructive (deletes data)

Only clear when:

Significant configuration change
Previous data no longer valid
Starting over with new approach

Don't clear if you just need to retry failures (use re-run instead)

Summary: Debugging Tools

You now have a complete debugging toolkit:

✅ Manual Re-run (3 modes):

Re-run empty cells (fill gaps)
Re-run failed cells (retry after fix)
Re-run all cells (recalculate everything)

✅ Clear and Reset:

Reset cells to empty
Delete data for fresh start
Understand downstream effects

✅ Cancel Tasks:

Stop queued/running cells
Prevent wasted API calls
Make changes mid-execution

✅ Real-Time Monitoring:

Visual state indicators
Column header summaries
Live updates

✅ Filtering:

Show only failures
Focus on specific states
Isolate problem rows

✅ Test Strategy:

Sample row testing
Safe configuration changes
Incremental validation

✅ Best practices:

Always test on samples first
Use appropriate re-run mode
Filter before bulk operations
Monitor and act fast
Clear sparingly

Next Steps

You've completed Chapter 11: Error Handling and Debugging! You now know:

What errors are and how to recognize them (11.1)
Systematic debugging workflow (11.2)
Complete toolkit for fixing issues (11.3)

Next: Chapter 12: Security and Access Control → Learn how to secure your automations, manage credentials, and implement access control.

Let's make your automations secure! 🔒

11.3 Debugging Tools ​

Overview of Available Tools ​

Your Debugging Toolkit ​

Tool 1: Manual Re-run ​

What It Does ​

Access Methods ​

Column Header Menu - Re-run Options

Row Selection - Context Menu

Re-run Modes Explained ​

Re-run Modes Comparison

Mode 1: Re-run Empty Cells

Mode 2: Re-run Failed Cells

Mode 3: Re-run All Cells

Quick Comparison

Mode 1: Re-run Empty Cells ​

Mode 2: Re-run Failed Cells ​

Mode 3: Re-run All Cells ​

Confirmation Dialogs ​

Standard Confirmation

Recalculate Column?

With Dependencies

Recalculate Column?

Monitoring Re-run Progress ​

Real-Time Column Progress

Execution Timeline

Cell State Indicators

Tool 2: Clear and Reset ​

What It Does ​

Access Method ​

Clear Menu - Reset Cell Data

Clear

Delete

Clear Operation Details ​

Clear Operation - What Happens

Before Clear

After Clear

What Changes During Clear

Clear Confirmation Dialog ​

Clear Confirmation Dialog

Clear all values in "company_data"?

Clear Workflow Example ​

Clear vs. Delete Column ​

Tool 3: Cancel Running Tasks ​

What It Does ​

Access Method ​

Cancel Menu - Stop Running Tasks

Cancel Behavior ​

Cancel Behavior - What Happens

Queued Cells

Running Cells

Completed Cells

Tool 4: Real-Time Monitoring ​

What It Provides ​

Cell State Indicators ​

Cell State Visual Reference

Column Header Summaries ​

Column Header Status Summaries

Real-Time Updates ​

Real-Time Updates - Live Progress

Example: Running 1,000 Cells

Tool 5: Filtering for Debugging ​

What It Does ​

How to Filter by State ​

Filter Modal - Focus on Problems

Configure Filters

Filtered Results - Focus on Failures

Before Filter1,000 rows

After Filter12 rows

Common Debugging Filters ​

Common Debugging Filters

Show Only Failures

Show Unprocessed

Show Rate Limited

Show Successful

Combine Multiple Filters

Clearing Filters ​

Tool 6: Test Strategy (Sample Row Testing) ​

What It Is ​

The Testing Workflow ​

Sample Testing Workflow

11.3 Debugging Tools

Overview of Available Tools

Your Debugging Toolkit

Tool 1: Manual Re-run

What It Does

Access Methods

Re-run Modes Explained

Mode 1: Re-run Empty Cells

Mode 2: Re-run Failed Cells

Mode 3: Re-run All Cells

Confirmation Dialogs

Monitoring Re-run Progress

Tool 2: Clear and Reset

What It Does

Access Method

Clear Operation Details

Clear Confirmation Dialog

Clear Workflow Example

Clear vs. Delete Column

Tool 3: Cancel Running Tasks

What It Does

Access Method

Cancel Behavior

Tool 4: Real-Time Monitoring

What It Provides

Cell State Indicators

Column Header Summaries

Real-Time Updates

Tool 5: Filtering for Debugging

What It Does

How to Filter by State

Common Debugging Filters

Clearing Filters

Tool 6: Test Strategy (Sample Row Testing)

What It Is

The Testing Workflow

Example: Testing Prompt Change

Debugging Tools Quick Reference

Best Practices for Using Debugging Tools

Practice 1: Always Test on Samples First

Practice 2: Use Appropriate Re-run Mode

Practice 3: Filter Before Bulk Operations

Practice 4: Monitor Real-Time, Act Fast

Practice 5: Use Clear Sparingly

Summary: Debugging Tools

Next Steps