Decaf Blog In-depth updates on Decaf software, tooling, and open-source experiments

ingestr v1.0.40 - Braze Source and KPI Window Fix

4 min read

ingestr v1.0.40 was published on June 23, 2026, with a small but useful release for data teams that move customer engagement data. The main change is a new Braze source, with a server connector catalog update so the source is visible through the connector surface, plus a KPI window fix that stops the start day from being dropped.

The full release notes and downloads are on the GitHub release page.

Braze source enters the ingestion path

The central item in v1.0.40 is the Braze source. The release notes name it plainly, and that is the change most likely to matter for ETL and ELT users.

The notes do not list Braze objects, endpoint coverage, or sync mode details. That limits what can be said responsibly. The safe read is that ingestr now has source code for Braze ingestion in this tag, and teams that already use ingestr can start evaluating Braze as another upstream system in the same toolchain.

For data engineers, the value is not that another connector exists in a catalog screenshot. It is that customer engagement data often sits beside product usage, billing, support, and warehouse identity tables. A Braze source gives teams a path to bring that data into the same pipeline layer as the rest of their operational sources, rather than handling it as a separate export job.

Server catalog wiring matters

The second Braze related change adds Braze to the server connector catalog. That is a separate operational detail from adding the source itself.

In practical terms, a connector that exists in code but is absent from a server catalog can be hard to discover, test, or expose through managed workflows. The release notes suggest v1.0.40 covers both halves: the Braze source and its catalog registration.

That matters for platform teams that standardize ingestion through a service layer. Catalog entries are often where internal users see what sources are available, and where platform code decides what can be configured. A missing catalog entry can turn a shipped connector into a local only feature. This release appears to avoid that gap for Braze.

KPI windows keep the start day

The non Braze fix in this tag addresses a KPI window bug where the start day was being dropped. That is a small bug on paper, but date window errors can produce visible reporting drift.

If a metric window starts on Monday and the code silently begins on Tuesday, the pipeline still runs. The output is just wrong by one day. That is the sort of defect that can survive longer than a failed job because it looks like a normal result until someone compares it against a source system or a finance report.

For warehouse users, this is worth checking after upgrade if any KPI tables or dashboards depend on date range boundaries. The release notes do not say the bug affects every connector or every KPI calculation. They do say the start day was being dropped, so the correct validation target is any metric that depends on inclusive window starts.

Review cleanup stayed narrow

The notes also say Greptile review feedback was addressed on the Braze source. They do not describe user visible behavior from that review pass.

That kind of entry is still useful signal. It says the new source had at least one focused review cleanup before the release was cut. It also suggests this tag is mostly connector addition plus targeted correctness work, not a broad platform refactor.

There are no breaking changes or migration steps listed in the notes. There are also no documented changes to CLI flags, destination behavior, authentication fields, or schema naming. Treat the Braze source as the main adoption item and the KPI window fix as the main correctness item, then test the exact Braze streams and date windows your pipelines depend on.

Where to get it