15.1 Real-Time Monitoring
Monitoring your automations in real-time helps you track progress, catch issues early, and ensure everything runs smoothly. This section shows you how to use the platform's visual monitoring tools.
Why Monitoring Matters
Without monitoring, you're flying blind:
- Can't tell if automations are working
- Don't know when errors occur
- Miss performance bottlenecks
- Can't plan capacity
With real-time monitoring, you have full visibility:
- Instant status updates
- Visual progress indicators
- Automatic error notifications
- Performance insights
Three Levels of Monitoring
The platform provides three levels of monitoring detail:
What: Status of all taibles
Where: Taibles list page
Use for: Quick health checks
What: Per-column metrics
Where: Column headers
Use for: Finding bottlenecks
What: Cell execution details
Where: Click any cell
Use for: Debugging issues
Level 1: Taible Overview
What you see: Status of all your taibles at a glance Where: Taibles list page Use for: Quick health checks, finding issues across projects
Level 2: Column Status
What you see: Progress for each processing step Where: Column headers in the grid Use for: Tracking which steps are running, finding bottlenecks
Level 3: Cell Details
What you see: Individual cell execution status and data Where: Click any cell in the grid Use for: Debugging specific issues, reviewing results
Level 1: Taible Overview
Understanding Status Indicators
Each taible shows a status indicator that tells you at a glance what's happening:
Completed (Green Checkmark)
All cells have finished processing successfully. No errors, no active work.
Processing (Animated Spinner)
Work is actively happening. Shows counts:
- Running: Currently executing
- Queued: Waiting to execute
Click to view the taible and see details.
Has Errors (Red)
Some cells have failed. Shows error count so you know how many need attention.
Rate Limited (Yellow)
Processing is temporarily slowed by rate limits. This is normal behavior to protect external APIs.
Inactive (Gray)
The taible exists but has no rows or no active processing.
Daily Health Check Routine
Start your day with a 5-minute check:
Scan for red indicators - These need immediate attention
- Click to view the taible
- Review error details
- Fix issues
Check blue spinners - Confirm things are running
- If nothing is running but should be, investigate
- Verify triggers are active
Review yellow warnings - Rate limits
- Normal if expected
- Too many? Consider adjusting limits
Verify critical taibles - Your most important automations
- Should show green checkmarks
- Check recent activity timestamps
Level 2: Column Status
Column Header Indicators
Each column header shows what's happening in that column:
Animated Spinner (Running)
At least one cell in this column is currently executing. Click the indicator to navigate directly to the running cell.
Clock with Number (Queued)
Shows how many cells are queued and waiting to execute. Hover to see details about the queue.
No Indicator
The column is idle with no active processing. This is the normal state when nothing needs to run.
Column Status Tooltip
Column Status Tooltip
Hover over a column header indicator to see:
- Which row is currently running
- How many cells are queued
- The next row that will execute
Click the indicator to jump directly to the active row.
Troubleshooting with Column Status
Symptoms: Same row running 5+ minutes
Cause: Row taking too long
Fix: Check timeout settings, consider canceling
Symptoms: Queue count keeps growing
Cause: Rate limits or slow processing
Fix: Adjust rate limits or concurrency
Symptoms: No indicator but rows exist
Cause: Configuration issue
Fix: Check run mode, conditions, dependencies
Scenario 1: Column Stuck on One Row
Symptoms: Spinner shows same row for 5+ minutes Diagnosis: That specific row is taking too long Actions:
- Click indicator to navigate to the row
- Check if the cell is actually running or hung
- Review timeout settings
- Consider canceling and re-running
Scenario 2: Large Queue Building Up
Symptoms: Queued count keeps growing (50, 100, 200+) Diagnosis: Rate limits or slow processing Actions:
- Review rate limit configuration
- Check if dependencies are slow
- Verify no errors blocking the queue
- Adjust concurrency if appropriate
Scenario 3: Nothing Processing
Symptoms: No indicator, but rows exist Diagnosis: Configuration issue preventing execution Actions:
- Check column run mode (Manual vs. Automatic)
- Review conditions (may be preventing execution)
- Verify dependencies are complete
- Manually trigger if needed
Level 3: Cell Status
Understanding Cell States
Each cell shows its current status with visual indicators:
Ready (Gray)
The cell hasn't been processed yet. Common reasons:
- Dependencies aren't complete yet
- Waiting for manual trigger
- Condition not met
- Just added
Queued (Blue with Clock)
The cell is waiting in the queue to execute. It will process automatically when ready.
Running (Animated Spinner)
The cell is currently executing. Duration varies by type:
- Simple calculations: Under 1 second
- API calls: 1-10 seconds
- AI operations: 2-30 seconds
Completed (Green with Data)
The cell executed successfully. Shows a preview of the result. Click to view full data.
Error (Red Badge)
Something went wrong. Shows error type and includes an eye icon to view details.
Rate Limited (Yellow)
The cell is waiting due to rate limit throttling. It will execute when the rate limit window opens. This is normal and automatic.
Scheduled (Purple)
The cell is waiting for an external event like a webhook or email. It will execute when the event occurs.
Skipped (Gray Italic)
The cell was intentionally skipped, either because:
- A condition evaluated to false
- Required dependencies are missing
Viewing Cell Data
{
"name": "Acme Corporation",
"domain": "acme.com",
"employees": 500,
"industry": "Technology"
}Last Updated: October 31, 2024 2:23 PM
Execution Time: 2.3 seconds
For completed cells (green), click to see:
Full Data Value The complete result, formatted based on type:
- Text: Full string
- Numbers: Formatted value
- Objects: JSON structure
- Arrays: All items
Metadata
- Last updated timestamp
- Execution time
- Who triggered it (if manual)
Actions
- Copy value to clipboard
- Re-run the cell
- Clear and reset to Ready
Error Details Sidebar
{
"error": {
"type": "unknown_record",
"message": "Company not found"
}
}{
"company_domain": "xyz-invalid.com",
"lead_email": "john@xyz-invalid.com"
}How to use error details:
- Description: Plain English explanation of what failed
- Technical Details: HTTP status and API endpoint information
- Input Data: Shows exactly what data was sent to the column
- Response Body: The error message returned by the API
When a cell shows an error, click the eye icon to open the error sidebar:
What you'll see:
Error Summary Type of error and status code
Description What went wrong in plain language
Input Data The data that was sent to the column (helps identify the problem)
Response Details (for API calls)
- HTTP method and URL
- Status code
- Response body
Actions
- Re-run the cell
- Clear to reset
- Copy error details
Common Error Types:
| Error Type | Common Cause | Solution |
|---|---|---|
| 404 Not Found | Resource doesn't exist | Check input data, verify API endpoint |
| 401 Unauthorized | Invalid API key | Update account credentials |
| 429 Too Many Requests | Rate limit exceeded | Add rate limiting configuration |
| Timeout | Request took too long | Increase timeout setting |
Monitoring Best Practices
Practice 1: Daily Scanning
Make it a habit (30 seconds per day):
- Open overview - Check all taibles
- Scan for red - Any errors?
- Verify critical taibles - Are they green?
- Check activity - Expected work running?
Result: Catch issues before they compound
Practice 2: Understand Your Baseline
Use this to detect anomalies:
Know what's normal for your automations:
Questions to answer:
- How long does a typical row take?
- What's a normal queue size?
- When do rate limits usually trigger?
- What's an acceptable error rate? (Aim for under 1%)
Example baseline:
Lead Enrichment:
- Typical row: 30-45 seconds
- Normal queue: 5-10 rows during business hours
- Rate limits: Hit around row 50
- Error rate: 2-3% (acceptable for external APIs)Use this to detect problems:
- Taking 5 minutes instead of 30 seconds? → Problem
- Queue at 100 instead of 10? → Investigate
- Error rate at 20%? → Something's wrong
Practice 3: Monitor Active Processing
Check that work is happening:
Good signs:
- Animated spinners indicate active work
- Queue counts show backlog being processed
- Timestamps are recent
Warning signs:
- No activity when you expect processing
- Queues growing instead of shrinking
- Same row running for too long
Action: Investigate triggers, dependencies, and conditions
Practice 4: Use Status for Performance Tuning
Find bottlenecks:
Identify slow columns Running indicator stays on one row too long
Measure impact Is it blocking other work?
Optimize
- Adjust timeouts
- Add rate limits if overwhelming APIs
- Cache repeated calls
- Split into parallel steps
Quick Reference
Taible-Level Status
| Indicator | Color | Meaning | Action |
|---|---|---|---|
| ✓ | Green | All complete | None (healthy) |
| ⟳ | Blue | Processing | Monitor progress |
| ✗ | Red | Errors present | Investigate immediately |
| ⚠️ | Yellow | Rate limited | Review if too slow |
| ○ | Gray | Inactive | None (intentional) |
Column-Level Status
| Indicator | Meaning | Action |
|---|---|---|
| ⟳ (animated) | Cell(s) running | Click to navigate to active cell |
| ⏱ 15 | 15 cells queued | Hover for details, monitor queue |
| (no indicator) | Idle, no activity | Normal state |
Cell-Level States
| State | Color | Icon | Meaning |
|---|---|---|---|
| Ready | Gray | — | Not processed yet |
| Queued | Blue | ⏱ | Waiting to execute |
| Running | Blue (pulse) | ⟳ | Currently executing |
| Completed | Green | ✓ | Success with data |
| Error | Red | ✗ | Execution failed |
| Rate Limited | Yellow | ⏸️ | Throttled by rate limit |
| Skipped | Gray | ⊘ | Intentionally skipped |
Summary
You now know how to monitor your automations:
✅ Three monitoring levels:
- Taible overview for portfolio health
- Column status for step-by-step progress
- Cell details for individual execution
✅ Visual indicators:
- Colors show status (green=good, red=error, blue=processing, yellow=throttled)
- Icons indicate state (spinner, clock, checkmark)
- Real-time updates (no refresh needed)
✅ Key practices:
- Scan overview daily for errors
- Check column headers for activity
- Click cells to debug issues
- Know your baseline performance
✅ Troubleshooting tools:
- Error sidebar for details
- Column tooltips for queue info
- Direct navigation to problem cells
Next Steps
Continue to: 15.2 Logs and History → Learn how to review past executions, audit trails, and change history for debugging and compliance.