16.2 Common Issues and Solutions
Even well-designed automations can encounter problems. This guide provides step-by-step solutions for the most common issues you'll face, with visual examples and clear diagnostics.
How to Troubleshoot Effectively
The Right Approach
Don't guess—diagnose systematically:
"Something's broken, let me try random changes until it works"
"Let me observe what's happening, find the root cause, and apply the right fix"
The Troubleshooting Process
Follow this pattern for every issue:
- Observe: What's actually happening?
- Compare: What should be happening?
- Diagnose: Why is there a difference?
- Fix: Apply the specific solution
- Verify: Did it work?
- Document: Note the problem and solution for future reference
Issue 1: Cells Stuck in "Queued" Status
What You'll See
Symptoms:
- Cells show blue "Queued" status with clock icon
- Status persists for extended time (5+ minutes)
- Column header shows large queue count
- Processing doesn't seem to advance
Example scenario: Your "Lead Enrichment" column shows 50 queued cells, but they've been waiting for several minutes without processing.
Step-by-Step Diagnosis
Step 1: Check Column Header Status
What to do:
- Find the column with queued cells
- Look at the column header for activity indicators
- Hover your mouse over any indicators you see
What the tooltip tells you:
- "Running: Row #34" = Processing IS happening (just might be slow)
- "Queued: 50 cells" = Number of cells waiting to process
- No running cell shown = Nothing executing (this is a problem!)
Step 2: Navigate to Active Cell
What to do:
- Click on the column header (where you see the queue indicator)
- The grid automatically navigates to the currently running cell
- Observe how long the cell has been processing
Timing expectations:
- Normal: 5-30 seconds for most operations
- Slow but OK: 30-60 seconds for AI analysis or heavy processing
- Stuck: 5+ minutes without completing (timeout issue)
Step 3: Identify the Root Cause
Now that you've observed the behavior, determine what's causing it:
Common Causes and Solutions
Cause A: Rate Limiting (Normal Behavior)
What you'll see:
- Some cells showing yellow "Rate Limited" status with pause icon
- Queue gradually decreasing
- Cells processing one at a time or in small batches
Why this happens: You've configured rate limits to prevent overwhelming external services. The system is working exactly as designed—it's intentionally slowing down to respect those limits.
What to do:
✓ No Action Needed
Optional: Speed up processing If you need faster processing and know your service can handle it:
- Right-click the column header
- Select "Edit Column"
- Navigate to "Rate Limits" section
- Increase the limits or adjust the time window
- Save changes
Cause B: Missing Dependencies
What you'll see:
- Queued cells that never progress
- Dependency columns showing errors or "Skipped" status
- Cells eventually change to gray "Skipped (Dependencies not present)"
Why this happens: A column depends on data from another column. If that dependency failed or was skipped, the dependent column can't run.
Example: Your "Lead Score" column needs data from "Company Data" column. But "Company Data" failed for some rows, so "Lead Score" can't calculate anything.
What to do:
Find the failed dependency:
- Look at which columns the stuck column depends on
- Check if any dependency columns have red "Unsuccessful" badges
Click on a failed cell in the dependency column
Click the eye icon to view error details
Fix the underlying problem:
- Invalid credentials? Update the account
- Service down? Wait for recovery
- Bad input data? Fix the source
- Timeout too short? Increase timeout setting
Re-run the fixed dependency:
- Right-click the cell
- Select "Re-run Cell"
- Watch it change: Queued → Running → Completed
Dependent cells automatically process:
- Once the dependency succeeds, the waiting cells will automatically queue and process
Cause C: Circular Dependency
What you'll see:
- Cells stuck in "Queued" indefinitely
- Two or more columns waiting on each other
- No progress in any of the involved columns
Why this happens: Column A depends on Column B, but Column B also depends on Column A. Neither can run because each is waiting for the other—a logical impossibility.
Example:
- "Lead Score" waits for "Company Data"
- "Company Data" waits for "Lead Score"
- Both stuck forever!
What to do:
Option 1: Remove unnecessary dependency
Often one dependency isn't actually needed:
- Edit one of the columns
- Check the Dependencies section
- Ask yourself: "Does this column really need that data?"
- Remove the unnecessary dependency
- Save—cycle broken!
Option 2: Reorder the logic
Break the process into non-circular steps:
Instead of:
- Step A → needs B
- Step B → needs A (circular!)
Do:
- Step A1 → no dependencies
- Step B → needs A1
- Step A2 → needs B (linear!)
Cause D: System Overload
What you'll see:
- ALL taibles showing large queues
- Everything processing extremely slowly
- Usually happens during peak usage or after bulk operations
Why this happens: Too many operations happening at once across your entire organization. The system is working through a backlog.
What to do:
Check if it's system-wide:
- Open several different taibles
- Check if they all show large queues
- If yes → system overload
- If only one taible → configuration issue (not overload)
Solution:
- Short queues (< 100 cells): Wait a few minutes—system will catch up
- Large queues (> 500 cells): May take 15-30 minutes
- Persistent for hours: Contact support
Quick Fix: Cancel and Restart
If cells are stuck and not progressing for no clear reason:
- Right-click the column header (with queue indicator)
- Select "Cancel Tasks"
- Confirm the cancellation
- All queued tasks return to their previous state
- Re-run the cells you need:
- Select the rows you want to process
- Right-click the column
- Select "Re-run Selected"
- Fresh queue starts processing
⚠️ When to Use This
Issue 2: High Failure Rate
What You'll See
Symptoms:
- Many cells showing red "Unsuccessful" badges
- Error rate suddenly increased (was <5%, now >10%)
- Similar errors across multiple cells
- Automation that previously worked now failing
Example scenario: Your "API Enrichment" column worked perfectly yesterday for 50 rows. Today, 45 out of 100 rows are failing with similar errors.
Step-by-Step Diagnosis
Step 1: Assess the Scope
What to do:
Filter to see only failures:
- Click the column header
- Look for filter or status options
- Select "Show only errors" or similar
Count the failures:
- How many failed out of total?
- Calculate: (Failed ÷ Total) × 100 = Error rate %
Check when failures started:
- Look at the timestamps on failed cells
- All today? → Recent problem
- Gradual increase? → Degrading issue
- Random over time? → Data quality issue
Step 2: Categorize the Errors
What to do:
- Click the first failed cell
- Click the eye icon to view error details
- Note the error type (see common types below)
- Check 5-10 more failed cells
- Determine pattern:
- All same error? → Systematic issue (configuration/service)
- Different errors? → Data-dependent issue (varies by row)
Common error types:
Common Causes and Solutions
Cause A: External Service Down
What you'll see:
- All failures started at the same time
- Errors showing "Service Unavailable" or "Internal Server Error"
- Affects all recent attempts, regardless of data
Why this happens: The external service (API, database, etc.) is temporarily down or having issues. Nothing you can do will fix this—you must wait for the service provider to resolve it.
What to do:
Verify service is down:
- Check the service's status page (e.g., status.servicename.com)
- Look for active incidents
Check estimated recovery time:
- < 1 hour: Just wait
- > 1 hour: Consider alternatives below
Options while waiting:
- Option A: Pause automation (disable trigger if active)
- Option B: Continue processing other columns
- Option C: Use alternative service if available
After recovery:
- Filter to show failed cells
- Select all failed cells
- Right-click → "Re-run Selected"
- Watch them succeed!
Cause B: Invalid Credentials
What you'll see:
- Errors showing "Unauthorized" or "Forbidden"
- All cells failing (not data-dependent)
- Started after credential change or expiration
Why this happens: Your account credentials for the service expired, were changed, or became invalid. The service is rejecting all requests because it can't verify your identity.
What to do:
Navigate to Settings:
- Click your profile icon
- Select "Settings"
- Go to "Accounts" or "Integrations"
Find the problem account:
- Look for the service you're using
- Check for warning indicators or expiration notices
Re-authenticate:
For OAuth services (Google, Facebook, etc.):
- Click "Re-authenticate" button
- Log in to the service
- Grant necessary permissions
- Token refreshed!
For API Key services:
- Generate new API key in the service's website
- Click "Edit" on the account
- Paste the new API key
- Save changes
Test with one cell:
- Find a failed cell
- Right-click → "Re-run Cell"
- Verify it succeeds with new credentials
Retry all failures:
- Select all failed cells
- Right-click → "Re-run Selected"
Cause C: API Changes
What you'll see:
- Errors showing "Not Found" or "Field not found"
- Started recently (after API provider update)
- Previously working configuration now fails
Why this happens: The service provider updated their API, changed endpoints, or modified data structures. Your configuration is trying to use the old API format that no longer exists.
What to do:
Check API provider's changelog:
- Visit the service's developer documentation
- Look for "What's New" or "Changelog"
- Identify breaking changes
Review the changes:
- Note new endpoint URLs
- Note changed field names
- Note new authentication requirements
Update column configuration:
- Right-click column header
- Select "Edit Column"
- Update configuration to match new API
- Save changes
Test with one cell:
- Re-run a single failed cell
- Verify it works with updated configuration
Retry all failed cells
💡 Need Help?
Cause D: Rate Limits Exceeded
What you'll see:
- Errors showing "Too Many Requests"
- Intermittent failures (some succeed, some fail)
- Happens during high-volume processing
Why this happens: You're sending requests to the external service faster than it allows. Each service has limits (e.g., "100 requests per hour"). When you exceed them, requests get rejected.
What to do:
Find the service's rate limits:
- Check the service's documentation
- Look for "Rate Limits" or "API Limits" section
- Note the limit (e.g., "20 requests per minute")
Add rate limiting to your column:
- Right-click column header → "Edit Column"
- Find "Rate Limits" section
- Enable rate limiting
- Set limit slightly below the service's limit
- Example: If service allows 100/hour, set to 90/hour for safety
Re-run failed cells:
- System will now throttle requests automatically
- Processing may be slower but won't fail
Example configuration:
- Service limit: 20 requests/minute
- Your setting: 18 requests per 1 minute
- Result: Safe, reliable processing
Cause E: Bad Input Data
What you'll see:
- Failures vary by row (not all cells fail)
- Errors showing "Invalid parameter" or "Validation failed"
- Some rows succeed, others fail with same configuration
Why this happens: The data in some rows doesn't meet the service's requirements. Empty fields, malformed emails, invalid formats—these cause the service to reject the request.
What to do:
Option 1: Fix the source data
Compare successful vs. failed rows:
- Look at input data for successful row
- Look at input data for failed row
- Identify the difference
Correct the data:
- Manually edit incorrect values
- Fix the upstream column producing bad data
- Update the data source
Re-run the fixed rows
Option 2: Add data validation
Prevent processing rows with invalid data:
- Edit the column
- Add a Condition
- Check for required data before processing
Example condition: "Only run if email field is not empty and contains @"
This skips rows with invalid data instead of trying to process them (and failing).
Option 3: Handle errors in processing
For advanced users using custom code, add error handling that gracefully manages invalid data and continues processing.
Issue 3: Automation Not Triggering
What You'll See
Symptoms:
- No new rows being created
- Trigger previously worked, now silent
- Expected data not arriving
- Last row created days ago
Example scenario: Your "Form Submissions" taible should receive 10-20 new rows per day from Typeform. But the last row was created 3 days ago.
Step-by-Step Diagnosis
Step 1: Check Trigger Status
What to do:
- Open the taible that should have trigger activity
- Open the Triggers panel (usually in right sidebar)
- Find your trigger in the list
- Check the status indicator:
- Green dot "Active" = Trigger is enabled and listening
- Gray dot "Inactive" = Trigger is disabled! (This is your problem)
Step 2: Verify Configuration
What to do:
- Click on the trigger to view details
- Check configuration based on trigger type:
For Webhook triggers:
- Webhook URL: Is it displayed?
- Status: Active or Inactive?
- Last triggered: When was it?
For Schedule triggers:
- Schedule: Is the timing correct?
- Last triggered: Did it run?
- Next trigger: When will it run?
For Email triggers:
- Check interval: How often does it check?
- Last checked: When was it?
- New emails found: Any?
Common Causes and Solutions
Cause A: Trigger Disabled
What you'll see:
- Status shows gray "Inactive" dot
- Trigger stopped at specific time (when disabled)
Why this happens: Someone manually disabled the trigger, or it was disabled due to errors.
What to do:
- Click on the inactive trigger
- Look for "Enable" button or toggle
- Click "Enable"
- Status changes to green "Active"
- Verify: Trigger will now process next event
Cause B: Webhook Not Configured at Source
What you'll see:
- Trigger is Active in Taibles
- No events being received
- Source service not sending webhooks
Why this happens: The trigger is listening, but the external service (Typeform, Shopify, etc.) hasn't been told where to send data. The webhook URL needs to be configured in the source service.
What to do:
Example: Typeform
- Copy webhook URL from Taibles trigger
- Log in to Typeform
- Open your form
- Click "Connect" → "Webhooks"
- Click "Add a webhook"
- Paste the Taibles webhook URL
- Select events: "Form submission"
- Save
Test:
- Submit a test form response
- Check: New row appears in Taibles!
💡 Different for Each Service
Cause C: Webhook URL Changed
What you'll see:
- Worked previously
- Stopped after trigger was modified
- Webhook URL in Taibles is different from URL in source service
Why this happens: If you recreated or modified the trigger, a new webhook URL was generated. The source service is still sending to the old URL (which no longer works).
What to do:
- Copy the new webhook URL from Taibles
- Log in to source service
- Find webhook configuration
- Update the URL:
- Remove old webhook
- Add new webhook with updated URL
- Save changes
- Test: Trigger an event and verify row creation
Cause D: Schedule Issues
What you'll see:
- Schedule trigger not firing at expected times
- Schedule looks correct but doesn't execute
Why this happens: Usually, the schedule is correct—you just haven't reached the trigger time yet. Or there might be a misunderstanding of the schedule syntax.
What to do:
Check the schedule:
- Daily at 9:00 AM
- Every Monday at 8:00 AM
- Every hour
- etc.
Check current time:
- If it's 2:00 PM and schedule is "Daily at 9:00 AM"
- Next trigger: Tomorrow at 9:00 AM
- This is correct—just waiting!
Test manually (don't wait):
- Look for "Test Trigger" or "Run Now" button
- Click to trigger immediately
- Verify automation works correctly
Verify schedule is what you want:
- If you need it to run now, modify the schedule
- If schedule is correct, just wait for next trigger time
Cause E: Email Account Connection Issues
What you'll see:
- Email trigger not checking inbox
- Email account credentials expired
- Authentication warnings
Why this happens: Email accounts require authentication. If credentials expire or change, the trigger can't access the inbox.
What to do:
- Go to Settings → Accounts
- Find the email account used by trigger
- Check status: Warning indicator?
- Click "Edit" or "Re-authenticate"
- Update credentials:
- Email address
- Password (use app-specific password for Gmail)
- Server settings (IMAP/SMTP)
- Save changes
- Test trigger:
- Send test email to monitored inbox
- Wait 1-2 minutes
- Verify row created
Issue 4: Unexpected Behavior
What You'll See
Symptoms:
- Column produces wrong output
- Data doesn't match expectations
- Logic seems backwards or missing
- Previously worked, now behaves differently
Example scenario:
- Expected: Lead score of 75 (high quality)
- Actual: Lead score of 0 (all leads scoring zero)
Or:
- Expected: Email sent to customer
- Actual: Email sent to wrong address
Step-by-Step Diagnosis
Step 1: Isolate the Problem
What to do:
Identify which column has unexpected behavior
Click a cell with wrong output
Review the output:
- What did you expect?
- What did you get?
- Is there an error? (No? Cell shows "Completed")
Check multiple rows:
- Is this affecting one row? → Data-specific issue
- Is this affecting all rows? → Configuration issue
- Is this affecting recent rows? → Recent change broke it
Step 2: Review Configuration
What to do:
- Right-click column header
- Select "Edit Column"
- Review each configuration section:
Input Fields:
- Are you pulling from the right columns?
- Are field names spelled correctly?
Conditions:
- Is the logic correct?
- Could the condition be failing unexpectedly?
- Try: Temporarily disable condition to test
Dependencies:
- Are you depending on the right columns?
- Is data from dependencies what you expected?
AI Instructions (for AI columns):
- Is the prompt clear and specific?
- Does it specify the output format?
- Were there recent changes?
Step 3: Test with Simple Data
What to do:
Create a test row with simple, known data:
- Email: test@example.com
- Company: Test Company
- Employees: 100
Run the column on this test row
Check result:
- Does it match your expectation?
- If YES: Column logic is correct, investigate data
- If NO: Configuration issue
Common Causes and Solutions
Cause A: Incorrect Field References
What you'll see:
- Output is empty or shows "null"
- Expected data not appearing
Why this happens: You're trying to use data from another column, but the field name is spelled wrong or doesn't exist.
What to do:
Edit the column with the problem
Find where you reference other columns
Check available fields:
- Click on the dependency column
- Look at its output
- Note the exact field names
Fix the reference:
- Correct spelling
- Match exact capitalization
- Use autocomplete if available
Save and re-run
Example fix:
- Wrong: [Company Employe Count] (typo)
- Right: [Company Employee Count]
Cause B: Condition Logic Error
What you'll see:
- Cells being skipped unexpectedly
- Condition evaluating opposite of your intent
Why this happens: The condition logic is backwards or incorrect.
What to do:
Edit the column
Review the condition
Read it carefully:
- What does it actually say?
- What did you intend it to say?
Common mistakes:
- Using "less than" when you meant "greater than"
- Using "AND" when you meant "OR"
- Using "equals" when you meant "contains"
Fix the logic
Save
Clear skipped cells:
- They'll re-evaluate with correct condition
Example fix:
- Wrong: Lead value less than 1000 → Runs for low-value leads
- Right: Lead value greater than 1000 → Runs for high-value leads
Cause C: Recent Configuration Change
What you'll see:
- Worked previously
- Started failing after specific date/time
- You (or someone) recently edited the column
Why this happens: A recent change to the configuration broke the column's logic.
What to do:
Export current taible (backup):
- Click taible menu
- Select "Export"
- Save file
Try to remember previous working configuration:
- What changed?
- What was the old setting?
Revert the change:
- Edit column
- Restore previous settings
- Save
Test with one cell
If works: Re-run all affected cells
📝 Track Changes
Quick Troubleshooting Reference
Use this quick reference to jump to solutions:
| What You See | Most Likely Cause | First Check | Quick Fix |
|---|---|---|---|
| Cells stuck "Queued" | Rate limiting or dependencies | Column header queue count | Wait or fix dependencies |
| Many cells showing errors | External service issue | Error message type | Re-authenticate or wait |
| No new rows from trigger | Trigger disabled or not configured | Trigger status (Active/Inactive) | Enable trigger or configure webhook |
| Wrong output | Field reference or condition error | Column configuration | Fix field names or logic |
| Cells showing "Skipped" | Condition not met | Condition logic | Review and adjust condition |
| Very slow processing | Dependencies or rate limits | Dependency chain | Optimize dependencies |
| All outputs are empty | Missing data or wrong reference | Input field configuration | Fix field references |
Summary: Systematic Troubleshooting
You now have systematic approaches for common issues:
✅ Cells stuck "Queued":
- Check for rate limiting (expected), dependencies (fix them), circular dependencies (break the cycle), or system overload (wait)
✅ High failure rate:
- Check for service outages (wait), expired credentials (re-authenticate), API changes (update config), rate limits (add throttling), or bad data (validate input)
✅ Trigger not working:
- Check if disabled (re-enable), webhook not configured (set it up), URL changed (update it), schedule timing (wait or test), or account issues (re-authenticate)
✅ Unexpected behavior:
- Check field references (fix typos), condition logic (correct logic), or recent changes (revert)
✅ Remember the process:
- Observe what's happening
- Compare to expected behavior
- Diagnose the root cause
- Apply specific fix
- Verify it worked
- Document for future
Next Steps
You've completed Section 16.2: Common Issues and Solutions!
What's next?
Continue to Chapter 17: Type System and Data Modeling to learn about advanced data handling, type systems, and structuring complex data in your automations.
Keep building! 🚀