Hi @MikeGo,

For both file arrival triggers and table update triggers, Databricks makes a best-effort check roughly every minute to detect new files or table updates. The end-to-end latency you should plan for is therefore on the order of 1-2 minutes, plus any time needed to start the job/cluster. There is no separate Databricks charge for these triggers themselves. The only incremental cost is from the cloud provider APIs used under the hood (for example, listing storage or reading table metadata). If you need sub-minute SLAs, we typically recommend a continuous stream (e.g., an Auto Loader with a short processing trigger) rather than relying solely on triggers.

Here is an official reference if you'd like to read further. 

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.