Laiki Changelog: workflows with publishing and version history
Workflows with a published version separate from editing and a version history, GA4 with more than 10 metrics, Meta Ads with up to 25 thousand rows, and a renewal warning.
Published on
2 min read
Laiki's weekly release, October 26, 2026: the biggest update is in workflows, which now separate the version that is running from the version you are editing. We also improved the ad data from Google Analytics 4 and Meta Ads and the way accounts stay connected.
Edit freely, publish when you are ready
A workflow's published version is now separate from the version being edited. Webhooks and schedules keep using the published version until you click Publish.
In practice, you can adjust a condition or swap an action calmly, without a half-finished change reaching the executions that are already happening.
Before you confirm publication, Laiki shows what changes. That way, you review the differences before they take effect.
If you need to take a workflow offline, use Unpublish. The next executions are stopped and everything is saved to publish again later. You can pause an automation without losing the configuration that has already been built.
Version history and publication log
The new Version history records each saved change on a timeline. With it, you can:
- open any older version;
- see what it changes compared to the current version;
- restore that version, if you want.
The Publications tab shows who published each version and when. If a workflow starts behaving differently, this log helps you find which publication changed what.
More complete ad data
Google Analytics 4 reports with more than 10 metrics now work. Those who need to cross-reference many metrics in the same report no longer have to split the analysis into smaller queries.
In Meta Ads, large queries bring up to 25 thousand rows and warn you when the result was cut off. Before, the result stopped at 5 thousand rows with no warning.
With the warning, it is clear when the query did not bring everything. This avoids drawing conclusions from part of the data thinking it is the total.
A warning before an account expires
Some platforms require you to log in again from time to time. When the deadline approaches, the credential shows "Renew by" with the date and a button to reconnect.
When you reconnect within the deadline, dashboards and workflows keep updating without interruption. You find out in advance which account needs attention, instead of discovering it when a number stops changing.
All of these improvements are already available in Laiki. To see the previous release, check the changelog for October 18.
