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
  • How it works
  • Using block windows
  1. Platform
  2. Connections

Block Window

Prevent executions from occurring during critical time windows.

PreviousColumn AnonymizationNextConnect to databases

Last updated 6 months ago

How it works

For various reasons, it may be necessary to ensure that no data extractions occur within a defined time window, thereby preserving resources from the source system.

To address this need, we offer the Block Window feature, which defines specific time intervals to restrict data extraction jobs. This functionality allows for precise control over execution times, ensuring resource optimization for the source system.

Configuration Options

The Block Window allows you to set:

  • Days: Define specific days when the restriction applies.

  • Start and End Times: Specify the time range for the block window.

Restriction Settings

You can further customize how the restriction is applied:

  1. Cancel running executions: Choose wheter to cancel previously started jobs executions.

  2. Allow Manual Executions: Choose whether to permit or block manually triggered jobs during the block window.

This feature provides flexibility and ensures optimal resource usage by aligning data extraction schedules with operational needs.

Using block windows