databricks Platform · Updated Jun 25, 2025

File arrival triggers with file events is now generally available

You can trigger job runs using file arrival triggers with file events on external locations, such as Amazon S3, Azure storage, or Google Cloud Storage.

GA Open docs ↗release note ↗

What it does

You can trigger job runs using file arrival triggers with file events on external locations, such as Amazon S3, Azure storage, or Google Cloud Storage. To benefit from this feature, the external locations must have file events enabled. File arrival triggers with file events allow a higher trigger limit (1,000 per workspace) and removes the 10,000 files per trigger limit.

Why it matters

How file arrival triggers work File arrival triggers make a best effort to check for new files every minute, although this can be affected by the performance of the underlying cloud storage.

Key capabilities

There no limits on the

There no limits on the number of files in the storage location.

Triggers can error on time

Triggers can error on time out when there are too many extraneous file updates.

If an existing file is

If an existing file is modified and its metadata falls outside the rolling retention period, that modification is treated as a…

A maximum of 50 jobs

A maximum of 50 jobs can be configured with a file arrival trigger on such locations in a Databricks workspace.

Architecture

Databricks Platform → Platform

In short

Read the full documentation ↗

Key takeaway

You can trigger job runs using file arrival triggers with file events on external locations, such as Amazon S3, Azure storage, or Google Cloud Storage.

2025-06-25-file-arrival-triggers-with-file-events-is-now-generally-available Generated by the Databricks Updates Agent · browse all updates