Accounts

Setting up scheduled jobs

Scheduled jobs let you run enrichments and processing actions automatically on a recurring or one-time basis. Instead of manually triggering runs against your tables, you configure the timing once and TexAu handles execution from there.

This guide walks you through every scheduling mode, the setup process, timezone handling, priorities, and practical patterns that work well for GTM teams.

What scheduled jobs do

A scheduled job ties a table (and optionally a filtered subset of its rows) to a timing configuration. When the scheduled time arrives, TexAu processes the designated rows through the columns and enrichments defined on that table.

Common use cases:

  • Enrich new leads every morning before your sales team starts work
  • Refresh company data every Monday to keep your CRM accurate
  • Run data processing every 30 minutes during business hours
  • Execute a one-time backfill of historical records on a specific date

The four scheduling modes

TexAu has four modes, each suited to a different cadence.

1. Once (single execution)

Runs your table processing at a specific date and time, then stops. The schedule moves to "Completed" status after execution.

Good for:

  • One-time data backfills
  • Processing a special dataset on a specific date
  • Testing a new enrichment before committing to a recurring schedule

What you configure:

  • Start date (calendar picker)
  • Start time (must be at least 5 minutes in the future)

2. At regular intervals

Runs your table processing every N minutes within an optional daily time window. This is the most flexible recurring mode.

Good for:

  • Near-real-time monitoring (every 10-15 minutes)
  • Frequent data refreshes during business hours
  • High-frequency processing with controlled windows

What you configure:

  • Interval in minutes (1 to 1,440)
  • Start time of daily window (optional, defaults to all day)
  • End time of daily window (optional)
  • Start date (optional, when the schedule begins)
  • End date (required, when the schedule stops)

Example: Run every 30 minutes between 9:00 AM and 5:00 PM, starting March 1 and ending March 31.

3. Every day

Runs your table processing once per day at a specific time.

Good for:

  • Daily lead enrichment before your team's workday
  • End-of-day data consolidation
  • Overnight processing of accumulated records

What you configure:

  • Time of day to run
  • Start date (optional)
  • End date (required)

Example: Run every day at 8:00 AM from now through the end of the quarter.

4. Days of the week

Runs your table processing on specific days at a specific time. You select which days (Sunday through Saturday) the job should execute.

Good for:

  • Weekly reports (e.g., every Monday)
  • Weekday-only enrichment (Monday through Friday)
  • Specific multi-day patterns (e.g., Tuesday and Thursday)

What you configure:

  • Days of the week (select one or more)
  • Time of day to run
  • Start date (optional)
  • End date (required)

Example: Run every Monday, Wednesday, and Friday at 2:00 PM through the end of Q2.

Setting up a scheduled job: step by step

Step 1: Navigate to the scheduler

From your table, open the scheduling options to create a new schedule. You can also access the Schedulers page from the main navigation to view all schedules across your workspace.

Step 2: Name your schedule

Enter a descriptive name. Good naming helps when you have multiple schedules running. Use names that describe the purpose:

This table scrolls sideways on small screens.

Instead ofUse
Schedule 1Daily Lead Enrichment - Sales Team
My jobWeekly Company Data Refresh
TestQ1 Backfill - Missing Phone Numbers

Step 3: Select your timezone

Choose the timezone that matches your working hours. TexAu shows a curated list of major timezones covering every region:

  • Americas (New York, Chicago, Denver, Los Angeles, Toronto, Vancouver, Sao Paulo, Mexico City)
  • Europe (London, Paris, Berlin, Madrid, Rome)
  • Africa (Cairo, Johannesburg)
  • Asia (Dubai, India, Karachi, Dhaka, Bangkok, Singapore, Hong Kong, Shanghai, Tokyo, Seoul)
  • Oceania (Sydney, Melbourne, Auckland)
  • UTC

The time you enter is interpreted in your selected timezone. If you select "India (IST)" and set a run time of 9:00 AM, the job runs at 9:00 AM India Standard Time.

Step 4: Choose your scheduling mode

Select one of the four modes: Once, At Regular Intervals, Every Day, or Days of the Week. The form updates to show the relevant fields for your chosen mode.

Step 5: Configure timing

Fill in the timing fields based on your mode (see the mode descriptions above). For recurring modes, an end date is always required so schedules don't run indefinitely.

For the "Once" mode, the start time must be at least 5 minutes in the future. If you select today's date, TexAu validates that the chosen time hasn't already passed in your selected timezone.

Step 6: Add filters (optional)

You can narrow which rows get processed each time the schedule runs. The filter builder lets you define conditions against your table columns using AND/OR logic.

Examples of useful filters:

  • Status equals "new" (only process unprocessed leads)
  • Created date equals today (only process today's additions)
  • Email is not empty (skip rows without email addresses)

Filtering is one of the most effective ways to reduce processing time and credit usage. Processing 50 new rows daily is far more efficient than reprocessing 10,000 rows every time.

Step 7: Save

Click Save to activate the schedule. It will begin running at the next scheduled time.

How timezone handling works

All scheduling in TexAu is timezone-aware and handles daylight saving time (DST) transitions automatically.

What happens behind the scenes:

  1. You pick a time in your local timezone (e.g., 9:00 AM Eastern)
  2. TexAu converts this to UTC for storage
  3. When the schedule fires, TexAu converts back to verify the correct local time
  4. During DST transitions, the conversion adjusts so your 9:00 AM job still runs at 9:00 AM local time

Things to keep in mind:

  • If you change your timezone after creating a schedule, any dates already selected may reset if they're now in the past for the new timezone
  • For "Days of the Week" schedules, timezone conversion may shift the day boundary (e.g., 11:00 PM Friday in New York is Saturday morning in UTC), but TexAu handles this correctly
  • Always double-check the timezone before saving, especially if your team spans multiple regions

Priority levels

When multiple schedules are set to run at the same time, TexAu uses priority to determine execution order.

This table scrolls sideways on small screens.

Priority rangeLabelWhen to use
8-10HighTime-sensitive enrichments your team depends on immediately
5-7MediumStandard recurring jobs (use this for most schedules)
1-4LowBackfills, non-urgent processing, background tasks

How priority works:

  • Higher-priority jobs execute first when competing for the same time slot
  • Jobs at the same priority run in the order they were created
  • Setting everything to high priority defeats the purpose, so reserve it for genuinely critical jobs

Schedule statuses

This table scrolls sideways on small screens.

StatusMeaningWhat to expect
ActiveSchedule is live and will run at the next scheduled timeNo action needed; check back after the scheduled time for results
InactiveSchedule is paused or disabledWon't run until reactivated
CompletedOne-time schedule has finished its executionNo further runs will occur
FailedMost recent execution hit an errorReview execution history for details; TexAu may auto-retry
PendingSchedule is created but waiting for its first execution timeEverything is configured correctly; wait for the scheduled time

Pausing and resuming schedules

Pausing

Click the pause action on any active schedule. The schedule moves to "Inactive" status and won't execute at its next scheduled time.

Good reasons to pause:

  • You're making changes to the underlying table structure
  • You need to troubleshoot unexpected results
  • You want to temporarily stop credit usage
  • External services you depend on are undergoing maintenance

If a job is currently executing when you pause, the current execution completes normally. Only future executions are prevented.

Resuming

Click the resume action on a paused schedule. It returns to "Active" status and will execute at its next scheduled time.

Resuming does not trigger an immediate execution. It simply reactivates the schedule for future runs. If you need to test immediately, run the table manually first.

Viewing history and logs

Click on any schedule to view its details, including:

  • Last run time: when the most recent execution occurred
  • Next execution: when the schedule will run next (for active schedules)
  • Total runs: the cumulative number of times this schedule has executed
  • Execution history: a chronological list of every run attempt

In the execution history, each entry shows:

This table scrolls sideways on small screens.

FieldDescription
Run timeWhen the execution started
StatusSuccess, partial, or failed
Rows processedHow many rows were included
DurationHow long the execution took
ErrorsDetails if something went wrong

Review execution history regularly to confirm your schedules are producing the expected results.

Common scheduling patterns

Daily lead enrichment

  • Mode: Every Day
  • Time: 8:00 AM (before your sales team starts)
  • Filter: Only rows where status equals "new"
  • Priority: High
  • Why it works: Sales reps get fresh, enriched lead data at the start of every workday without lifting a finger.

Weekly data refresh

  • Mode: Days of the Week (Monday only)
  • Time: 8:00 PM Sunday
  • Filter: All rows
  • Priority: Medium
  • Why it works: Running overnight on Sunday means the refresh completes before Monday morning, without competing with weekday jobs.

Business-hours monitoring

  • Mode: At Regular Intervals
  • Interval: Every 30 minutes
  • Window: 9:00 AM to 6:00 PM
  • Filter: Rows marked for monitoring
  • Priority: Medium-high
  • Why it works: Keeps data near-real-time during working hours without burning credits overnight.

One-time historical backfill

  • Mode: Once
  • Date/Time: A specific upcoming date during off-peak hours
  • Filter: Rows from a particular date range or import batch
  • Priority: Low
  • Why it works: Processes historical data without interfering with your team's regular enrichment schedules.

Advanced: cron expressions

Under the hood, recurring schedules use cron expressions to define their timing. The scheduling form handles this for you, but understanding cron syntax can be helpful for interpreting schedule configurations.

Standard cron format: minute hour day-of-month month day-of-week

This table scrolls sideways on small screens.

ExpressionMeaning
0 9 * * *Every day at 9:00 AM
0 9 * * 1Every Monday at 9:00 AM
*/30 9-17 * * *Every 30 minutes between 9:00 AM and 5:00 PM
0 8 1 * *First day of every month at 8:00 AM
0 9 * * 1,3,5Monday, Wednesday, and Friday at 9:00 AM

All cron expressions are stored in UTC internally. TexAu converts between your local timezone and UTC automatically when building and interpreting these expressions.

Most users won't ever need to write cron expressions directly. The four scheduling modes in the form cover the vast majority of use cases.

What happens when a scheduled job fails

When an execution hits an error, TexAu follows this sequence:

  1. The execution is logged with a "Failed" status and error details
  2. TexAu retries the execution with increasing wait times between attempts
  3. Failed executions appear in your schedule's execution history
  4. If all retry attempts fail, the execution is marked as permanently failed

Common failure causes and what to do:

This table scrolls sideways on small screens.

CauseWhat happensRecommended action
External service temporarily unavailableAuto-retry usually resolves itCheck execution history; if retries succeeded, no action needed
Rate limits exceededRetries with backoff respect the limitsConsider reducing schedule frequency or processing fewer rows per run
Invalid data in a columnProcessing fails for affected rowsReview the failing rows, fix the data, then let the next scheduled run pick them up
Table structure changedSchedule may fail if expected columns are missingUpdate the table to restore expected columns, or recreate the schedule

Check your execution logs after failures to understand the root cause. Most transient issues (network blips, temporary service outages) resolve automatically through retries.

Plan limits

Different plan tiers have different scheduling capabilities. The main constraints are how frequently you can schedule recurring jobs and how many active schedules you can maintain at once.

This table scrolls sideways on small screens.

Plan tierMinimum intervalMax active schedules
BasicDailyLimited
Mid-tierEvery few hoursModerate
Higher-tierHourly or more frequentGenerous or unlimited

If you need more frequent scheduling or more concurrent schedules, review your current plan in Settings to see your options.

Tips for efficient scheduling

  1. Always use filters. Processing only the rows that need it (e.g., rows added since the last run) is faster and uses fewer credits than reprocessing your entire table.

  2. Start with a longer interval, then tighten. Begin with daily schedules. Once you confirm everything works correctly, increase the frequency if your use case demands it.

  3. Run your table manually first. Before scheduling, execute a manual run to verify that your enrichments, formulas, and processing actions produce the expected results.

  4. Stagger overlapping schedules. If you have three daily jobs, schedule them at 8:00 AM, 8:30 AM, and 9:00 AM rather than all at 8:00 AM. This reduces resource contention.

  5. Set realistic priorities. Most jobs should be medium priority. Only mark a job as high priority if delayed execution would directly impact your team's workflow.

  6. Combine related operations in one table. Instead of scheduling five separate tables that each process a different aspect of the same data, consolidate into one table with multiple enrichment columns. One schedule replaces five.

  7. Name schedules descriptively. When you have 15 active schedules, names like "Daily Lead Enrichment - Sales" and "Weekly Refresh - Company Database" are far easier to manage than "Schedule 1" and "My Job."

  8. Set end dates thoughtfully. Recurring schedules require an end date. Set it far enough in the future to avoid unexpected stops, but review and extend periodically so you don't forget about stale schedules.


Next steps