The Time window and offset setting on the Asset Overview will be deprecated soon. What this means:

• This change will not affect any existing monitors.
• The configuration is now available directly in the Monitor creation flow.

The equivalent options are now available in the Monitor creation flow under the incremental scan configuration in advance settings.

• First run time window
• Time offset amount

These provide more flexible and precise controls.

📖 Learn more in the documentation.

✨What’s new

Users can now define a custom expiration delay for access tokens, overriding the default 24-month validity.

⏱️ Custom expiration settings

• Users can set a custom expiration duration (e.g. 45 days, 3 months).
• Default expiration remains 24 months if no custom value is set.

Version 607

We’ve introduced two major enhancements to our custom monitoring capabilities, giving you granular control over how you aggregate metrics and define row-level failure conditions using SQL.

What’s New?

• Custom Aggregation for Metrics Monitors: You are no longer limited to built-in functions like SUM or AVG. You can now write custom SQL aggregations to calculate unique numerical values, such as MEDIAN() or complex ratios across joined datasets (e.g., SUM(datasetA:field1) / SUM(datasetB:field2)).

• SQL Condition Custom Monitor: For complex logic that goes beyond our No-Code Condition builder, the new SQL Condition monitor allows you to define failure criteria using a SQL boolean expression. If a row evaluates to TRUE, an anomaly is triggered.

  Unlike the SQL Query Custom monitor, this monitor benefits from the same features as the other monitor types : Time Settings, Where Clause, Group By,...

ℹ️ Key Technical Notes:

Field Formatting: To reference fields in these SQL editors, use the format datasetId:fieldName.

UI Autocomplete: Simply start typing your table or field name in the editor, and Sifflet will automatically suggest the correctly formatted ID for you.

Scope: Queries must be performed on the datasets already selected in your join clause; querying external tables within the SQL snippet is not supported.

Version:v608

As organizations grow, maintaining access and ownership for every individual user becomes a bottleneck. We are excited to introduce Teams—a new way to mirror your company’s real-world structure directly within the platform.

What’s new?

You can now group users into Teams to manage permissions and ownership once — and apply them automatically to everyone in the group.

• Onboard new users faster with instant, team-level access
• Update permissions for an entire team in one action
• Clarify ownership across Domains, Assets and Incidents
• Built to reflect how your teams actually work

👉 Check this document to learn more.

Version:v603

Sifflet now automatically synchronizes your account timezone with your local browser timezone upon first login.

New users no longer need to manually select a timezone; Sifflet detects your browser’s settings to ensure all incident data and schedules are displayed in your local time.

ℹ Impact on Existing Users: If you haven’t previously updated your timezone in your profile settings, your account will now automatically match your current browser timezone.

Manual Overrides: You still have full control to manually change your timezone at any time via the User Profile icon in the top-right corner of the Sifflet application.

Version:v599

In Sifflet, we’ve started improving the Lineage experience! You can now navigate your data structures more easily—no more scrolling through endless lists to find the right data point. This is just one of many enhancements we’ll be rolling out in the future.

What’s New?

Column Search: Quickly find specific columns within any table using the new search bar.

Table Pagination: For tables with extensive schemas , we’ve introduced pagination. You can now flip through pages of columns easily using the new navigation arrows at the bottom of the drawer.

App Version: v598

✨ What’s new

You can now connect Jira using OAuth, alongside the existing authentication method. OAuth offers improved security and reliability.

👉 Check this document to learn more.

App Version: v590

We are excited to launch Subdomains, which provide hierarchical organization and finer access control across your Parent Domains. This helps teams stay structured, manage access complexity, and ensure specific data assets are only visible to the relevant users.

🚀 Key Benefits

• Granular Access: Limit access to specific assets and users within a large domain.
• Hierarchical Structure: Organize complex domains (e.g., "Marketing" divided into "Brand Marketing" and "Digital Marketing").
• Streamlined Management: Simplify domain maintenance by delegating ownership to smaller units.

You can now enforce more predictable data standards with our Static Threshold option for Metadata Freshness monitors (update-time-gap-based freshness). Instead of relying solely on dynamic, machine-learning-driven deviation, you can set a fixed, maximum (and/or minimum) acceptable time-lag (e.g., "Alert me if the table's metadata hasn't been updated in over 12 hours").

• This provides greater control and certainty when monitoring business-critical tables with well-defined latency SLAs.
• Find the new setting within the monitor configuration panel under the "Threshold settings" section.

App Version: v576

We introduced a new event scope option for webhooks called “All events.”

With this setting, the webhook will receive every event generated in Sifflet, regardless of whether the event is linked to a specific monitor, source, or asset.

What’s the difference from the existing scope?

• Linked events (existing)

  Only sends events related to elements explicitly configured with the webhook — for example, specific monitors or sources selected by the user.

• All events (new)

  Sends all events across the platform to the webhook URL, without needing to link specific elements. Ideal for users who want a single webhook endpoint to capture everything for centralized processing.

  This can be useful for you if you want to retrieve real-time data about our monitor runs. It also serves as an alternative to our Public API Rules.