Once your schedules are running, you need visibility into their performance and the ability to adjust them as your needs change. This guide covers the Schedulers dashboard, editing and controlling schedules, monitoring health, handling failures, and keeping your automation efficient over time.
Viewing all your schedules
The schedulers dashboard
Navigate to the Schedulers page from the main sidebar. You'll see a table listing every schedule in your workspace with these columns:
This table scrolls sideways on small screens.
| Column | What it shows |
|---|---|
| Name | The schedule name you assigned |
| Table Associated | Which table the schedule runs against (clickable link to the table) |
| Status | Active or Inactive |
| Total Run | How many times this schedule has executed |
| Mode | Once or Interval |
| Actions | History, Edit, and Delete buttons |
Click any row to open a details sidebar showing the full schedule configuration, including timezone, next execution time, start and end dates, and any applied filters.
Filtering and sorting schedules
When you have many schedules, use these approaches to find what you need:
- Filter by status to focus on Active or Inactive schedules.
- Sort by column by clicking column headers (name, status, total runs, or mode).
- Search by name. Use descriptive schedule names so you can locate them quickly. Names like "Daily Lead Enrichment - Sales Team" are far easier to find than "Schedule 1."
Editing schedule timing and configuration
Click the Edit (pencil icon) action on any schedule to open the editing modal. The modal loads the current configuration so you can see exactly what's set before making changes.
What you can edit
- Schedule name —rename anytime to keep things organized.
- Timezone —change if your team relocates or if you want the schedule aligned to a different region. Changing the timezone may reset date fields if the currently selected dates would be in the past for the new timezone.
- Scheduling mode —switch between Once, At Regular Intervals, Every Day, and Days of the Week. Each mode shows different configuration fields.
- Timing details —adjust the specific date, time, interval, daily window, or selected days depending on the mode.
- Filters —add, modify, or remove row filter conditions. The filter builder shows your table's columns so you can create precise AND/OR conditions.
- Start and end dates —adjust the active window for recurring schedules. End date is required for all recurring modes.
What you cannot edit
The associated table is fixed at creation. To schedule a different table, create a new schedule.
How edits take effect
Changes apply on the next scheduled execution, not immediately. If you want to verify your changes work correctly, run the table manually before the next scheduled time.
If you're editing a recurring schedule and the updated configuration produces a different cron expression (for example, changing from "Every Day at 9 AM" to "Every Day at 2 PM"), TexAu recalculates the next execution time based on your new settings.
Pausing schedules
When to pause
- You're troubleshooting unexpected results and want to stop runs while you investigate.
- The underlying table structure is being modified (adding or removing columns).
- External services your enrichments depend on are undergoing maintenance.
- You need to temporarily reduce credit usage.
- You're making workflow changes and don't want the schedule to fire mid-update.
How to pause
Click the row for the schedule to open its details sidebar, or use the edit action. Change the schedule status to inactive.
What happens when you pause:
- If an execution is currently in progress, it completes normally. Pausing does not cancel running jobs.
- No new executions will start.
- The schedule remains in your list with "Inactive" status.
- All configuration (timing, filters, priority) is preserved exactly as-is.
- You can resume at any time.
Resuming paused schedules
Reactivate a paused schedule by changing its status back to active. The schedule picks up from its next scheduled time. It does not retroactively run any executions that were missed while paused.
Example:
- You pause a daily 9:00 AM schedule on Wednesday.
- You resume it on Friday morning at 8:00 AM.
- The next execution runs Friday at 9:00 AM (not immediately when you resume, and not for Thursday's missed run).
If you need an immediate execution after resuming, run the table manually. The schedule will then continue on its regular cadence from the next scheduled time.
Deleting schedules
How to delete
Click the Delete (trash icon) action on any schedule. A confirmation dialog appears:
"Are you sure you want to delete [schedule name]? This action cannot be undone."
Click Delete to confirm, or Cancel to back out.
What happens when you delete
- The schedule is permanently removed from your workspace.
- No further executions will occur.
- Execution history for that schedule is no longer accessible.
- There is no undo or recovery option.
When to delete vs. pause
This table scrolls sideways on small screens.
| Situation | Recommended action |
|---|---|
| Temporary stop (days to weeks) | Pause |
| No longer need this schedule at all | Delete |
| Consolidating multiple schedules into one | Delete the old ones after the new one is confirmed working |
| Troubleshooting a problem | Pause first; delete only if the schedule is no longer needed |
| Table has been removed | Delete the orphaned schedule |
If you're unsure, pause first. You can always delete later, but you can't recover a deleted schedule.
Understanding execution history
Viewing the history
Click the History (clock icon) action on any schedule to open the execution history sidebar. This shows a chronological list of every run attempt.
Each entry displays:
This table scrolls sideways on small screens.
| Field | Description |
|---|---|
| Run time | When the execution started |
| Status | Whether it succeeded, partially completed, or failed |
| Rows processed | How many rows were included in the run |
| Duration | How long the execution took from start to finish |
| Errors | Specific error information if something went wrong |
What each status means
This table scrolls sideways on small screens.
| Status | Meaning | Recommended action |
|---|---|---|
| Success | All designated rows were processed without errors | No action needed |
| Partial | Some rows were processed but others hit errors | Review error details; fix affected rows or data; the next run will reprocess |
| Failed | The execution could not complete | Check error logs; TexAu may auto-retry; see the failure handling section below |
| Skipped | The scheduled time passed while the schedule was paused | Resume the schedule if you want future runs to proceed |
Reviewing individual run details
Click into any execution entry to see the full details:
- Exact start and end timestamps down to the second
- Row-level results showing which rows succeeded and which failed
- Error messages with specifics about what went wrong
- Step-by-step execution log showing the sequence of operations
This level of detail is useful for diagnosing issues and understanding how your schedules perform over time.
Monitoring schedule health
Healthy schedules run consistently, complete successfully, and finish in a predictable amount of time. Here are the indicators to watch.
1. Consistency
Check the "Last Run" information against when you expect the schedule to have executed. If a daily 9:00 AM schedule shows its last run as two days ago, something may be wrong (paused status, failure, or configuration issue).
2. Success rate
Occasional failures are normal. External services have outages, rate limits get hit, and network issues happen. But if you see multiple consecutive failures or a success rate below 90%, investigate promptly.
3. Execution time
Track how long each run takes. A schedule that used to complete in 2 minutes but now takes 15 minutes may indicate:
- Your table has grown significantly (more rows to process)
- External services are responding slower than usual
- New enrichment columns were added, increasing processing per row
Gradual increases tied to data growth are expected. Sudden jumps warrant investigation.
4. Error patterns
Look for recurring themes in error messages:
- Same error every run —likely a configuration or data issue you need to fix.
- Intermittent errors —probably transient (network, rate limits). Auto-retry usually resolves these.
- Errors increasing over time —may indicate a growing data quality problem or an external service becoming less reliable.
Monthly health checks
Set a recurring reminder to review your schedules once a month. Here's a simple checklist:
- Review all Active schedules. Are they all still needed? Remove or pause any that aren't serving a purpose.
- Check the last 10 executions for each schedule. Are they mostly successful? Note any with repeated failures.
- Verify execution times. Are they within the expected range? Flag any that have grown significantly.
- Spot-check one result. Pick a recent execution, open the details, and verify the processed data looks correct.
- Review end dates. For recurring schedules, make sure end dates are still in the future. Extend any that are approaching expiration.
- Consolidate if possible. If you have multiple small schedules running against the same table, consider combining them.
What happens when a scheduled job fails
Automatic retry behavior
When an execution fails, TexAu automatically retries with exponential backoff:
This table scrolls sideways on small screens.
| Attempt | Wait before retry |
|---|---|
| 1st retry | 5 minutes |
| 2nd retry | 30 minutes |
| 3rd retry | 4 hours |
If all retry attempts fail, the execution is marked as permanently failed. The schedule itself remains active and will attempt its next regular execution at the scheduled time.
Common scenarios where auto-retry helps:
- An external data provider was briefly unavailable. The retry 5 minutes later succeeds because the service recovered.
- A rate limit was hit. The 30-minute wait allows the rate limit window to reset.
- A brief network disruption interrupted the run. The next retry connects normally.
Manual retry
If auto-retry didn't resolve the issue:
- Open the schedule's execution history.
- Review the error details on the failed execution to understand the root cause.
- Fix the underlying problem (data issue, table configuration, etc.).
- Run the table manually to verify the fix works.
- The next scheduled execution will proceed normally.
Common failure causes and solutions
This table scrolls sideways on small screens.
| Problem | Likely cause | Solution |
|---|---|---|
| External service unavailable | Provider outage or maintenance | Wait for auto-retry. Check the provider's status page if retries keep failing. |
| Rate limit exceeded | Too many requests in a short window | Reduce the number of rows per run using filters, or increase the interval between runs. |
| Invalid data in processed rows | Unexpected values in columns that enrichments or formulas depend on | Review the failing rows. Clean up or correct the problematic data. |
| Table structure mismatch | Columns were renamed or removed after the schedule was created | Update the table to restore expected columns, or recreate the schedule. |
| Timeout | Large number of rows or slow external responses | Process fewer rows per run by tightening your filters. Consider breaking one large schedule into several smaller, staggered ones. |
| Authentication expired | Credentials for a connected integration lapsed | Reconnect the integration in Settings, then let the next run proceed. |
Schedule limits by plan tier
Different plan tiers have different scheduling capabilities. The main constraints are minimum interval frequency and the number of active schedules you can run at once.
This table scrolls sideways on small screens.
| Plan tier | Minimum interval | Max active schedules | Typical use case |
|---|---|---|---|
| Basic | Daily | A small number | Individual users running daily enrichments |
| Mid-tier | Every few hours | A moderate number | Growing teams with multiple workflows |
| Higher-tier | Hourly or more frequent | Generous or unlimited | Organizations with high-volume, time-sensitive automation |
To see your current limits, check Settings in your workspace. If your scheduling needs exceed your current plan, review the available upgrade options there.
Tips for efficient scheduling
1. Start conservative, scale up gradually
Begin with daily schedules. Monitor results for a week to confirm everything works correctly. Only then increase frequency. Jumping straight to every-15-minutes scheduling without validating your setup wastes credits and can mask problems.
2. Use filters to process only relevant rows
The single most impactful optimization. Instead of processing your entire table every run, use filter conditions to target only the rows that need processing.
Less efficient: Process all 10,000 rows daily. More efficient: Process only rows where "status equals new" —typically 50-100 rows daily.
The second approach runs faster, uses fewer credits, and produces cleaner execution logs.
3. Stagger your schedules
If you have multiple schedules, spread them across different times rather than clustering them together.
Instead of:
- Schedule A: 9:00 AM
- Schedule B: 9:00 AM
- Schedule C: 9:00 AM
Do:
- Schedule A: 8:00 AM
- Schedule B: 9:00 AM
- Schedule C: 10:00 AM
Staggering prevents all your jobs from competing for resources at the same time and makes it easier to trace issues to specific schedules.
4. Set appropriate priorities
Reserve high priority for schedules where delayed execution directly impacts your team. Most schedules should be medium priority.
This table scrolls sideways on small screens.
| Priority | When to use |
|---|---|
| High (8-10) | Morning lead enrichment that sales reps depend on at 9 AM |
| Medium (5-7) | Standard recurring data refreshes and maintenance |
| Low (1-4) | Background backfills, non-urgent cleanup, experimental schedules |
5. Monitor execution times
Keep an eye on the duration column in execution history.
This table scrolls sideways on small screens.
| Duration | Assessment |
|---|---|
| Under 1 minute | Very efficient |
| 1-10 minutes | Normal for most schedules |
| 10-30 minutes | Acceptable for large datasets; watch for growth |
| Over 30 minutes | Investigate —consider tighter filters or splitting into smaller schedules |
6. Combine related operations
If you have multiple schedules running against the same table at similar times, consolidate them. One table with five enrichment columns running on one schedule is more efficient than five separate schedules each processing one column.
7. Document your schedules
For teams with many active schedules, maintain a simple reference:
This table scrolls sideways on small screens.
| Schedule | Frequency | Purpose | Owner |
|---|---|---|---|
| Daily Lead Enrichment | Every Day, 8 AM | Fresh data for sales reps | Marketing Ops |
| Weekly Company Refresh | Monday, 8 PM | Baseline company data update | Data Team |
| Hourly Monitoring | Every 30 min, 9 AM-6 PM | Near-real-time pipeline updates | RevOps |
This helps when onboarding new team members, auditing credit usage, or troubleshooting unexpected behavior.
8. Use clear, descriptive names
Your schedule name should answer "what does this do?" at a glance.
Avoid: "Test," "Schedule 1," "My Workflow" Prefer: "Daily Lead Enrichment - Inbound," "Weekly Data Refresh - Company DB," "Q1 Backfill - Missing Emails"
Troubleshooting common issues
Schedule is not running
- Check the status. Is it Active or Inactive? An Inactive schedule won't execute.
- Check the end date. Has the end date passed? Recurring schedules stop running after their end date.
- Check execution history. The schedule may have run successfully but produced no visible changes (e.g., the filter matched zero rows).
- Verify the timing. For a "Days of the Week" schedule, confirm today is one of the selected days. For an interval schedule, confirm you're within the daily time window.
- Check the timezone. A schedule set to 9:00 AM Pacific won't run at 9:00 AM Eastern. Verify the timezone matches your expectations.
Schedule is running but results look wrong
- Review which rows were processed. Open execution history and check the row count. If fewer rows than expected were processed, your filter conditions may be too restrictive.
- Check filter conditions. Open the schedule editor and review the filter builder. Are the column references correct? Are the operators and values what you intend?
- Run the table manually. Process the same rows manually to see if the issue is with the schedule configuration or the underlying table setup.
- Verify enrichment and formula configuration. The schedule runs whatever is configured on the table. If the table's enrichments are misconfigured, the schedule will produce incorrect results.
Scheduled job takes much longer than expected
- Check your data volume. Has the table grown significantly? More rows means longer processing.
- Review your filters. If you're processing all rows instead of a filtered subset, consider adding a filter.
- Check external service performance. Slow responses from data providers increase total execution time.
- Look for new columns. If someone added new enrichment columns to the table, each row now requires additional processing.
Getting repeated failures
- Read the error message. The execution history has specific error details. Start there.
- Distinguish between internal and external issues. If the error references an external service, check that service's status. If the error is about your data or configuration, fix it directly.
- Pause the schedule while you investigate and fix the issue. This prevents wasted retry attempts.
- Test manually after fixing. Run the table manually to confirm the fix resolves the problem.
- Resume the schedule once the manual run succeeds.
Next steps
- Need to create a new schedule? Setting Up Scheduled Jobs
- Want to prepare your data with formulas before scheduling? Formula Basics
- Looking to add processing actions to your scheduled tables? Built-in Processing Actions