LogoLogo
  • Introduction
    • Welcome
    • Quickstart
  • Platform
    • Connections
      • Jobs
      • Sync types
      • Sync schedule
      • Column Anonymization
      • Block Window
    • Connect to databases
    • Running jobs manually
    • Alert Integrations
      • Discord
      • Email
      • Slack
    • Runs history
    • How we move data
  • Connectors
    • APIs
      • ActiveCampaign
      • Amplitude
      • Asaas
      • Asana
      • Bling
      • Beehiiv
      • BomControle
      • Campaign Monitor
      • ClickUp
      • Conta Azul
      • Convenia
      • CustomerX
      • Delighted
      • Facebook Ads
      • FreshChat
      • Freshdesk
      • Gainsight
      • Google Ads
      • Hotmart
      • HubSpot
      • Intercom
      • Jira
      • Linkedin Ads
      • MailChimp
      • MailGun
      • MercadoLibre
      • Mixpanel
      • Monday
      • Movidesk
      • Omie
      • Pipefy
      • Qulture.Rocks
      • RD Station CRM
      • RD Station Marketing
      • Sankhya
      • Sentry
      • Stripe
      • Superlógica
      • Tiny
      • Teamwork Desk
      • Track.co
      • Twitch.tv
      • Twygo
      • Typeform
      • Vindi
      • Zendesk
    • Databases
      • Firebird
      • MySQL
      • Neo4j
      • Oracle
      • PostgreSQL
  • Destinations
    • BigQuery
      • Hosted by Erathos
    • Databricks
    • PostgreSQL
      • Aws (RDS)
      • Azure
    • Redshift
    • S3 Iceberg
  • API
    • Introduction
      • Trigger jobs outside Erathos
      • Trigger jobs in Erathos
    • Quickstart
      • Airflow
      • Dbt Cloud
      • Erathos
      • Prefect
    • Concepts
      • Authentication
      • Metadata
      • Rules
      • Variables and secrets
    • API Reference
      • Jobs
      • Orchestration
      • Secrets
      • Variables
      • Workspaces
  • Settings
    • User settings
    • Workspace settings
Powered by GitBook
On this page
  • Base hour
  • Frequency
  • Using sync frequencies and base hour
  1. Platform
  2. Connections

Sync schedule

Define the schedule on which the jobs will be executed

The primary function of a data pipeline is to keep two environments synchronized. To achieve this, pipelines rely on scheduled data update executions. These schedules are typically based on a specific time and an update frequency.

Base hour

The Base Hour refers to the specific time of day at which a scheduled pipeline execution begins, serving as the anchor point for the selected update frequency (e.g., weekly, daily, or every 12 hours). All subsequent executions follow this base hour based on the defined frequency.

Frequency

The available update frequencies on the Alexandria platform are:

  • Manually: Executes only when trigged by user.

  • Weekly: Executes once every week.

  • Daily: Executes every 24 hours.

  • Every 12 Hours: Executes every 12 hours.

  • Every 6 Hours: Executes every 6 hours.

  • Every 3 Hours: Executes every 3 hours.

  • Every Hour: Executes every 1 hour.

  • Every 30 Minutes: Executes every 30 minutes.

Using sync frequencies and base hour

PreviousSync typesNextColumn Anonymization

Last updated 6 months ago