.png?width=315&height=83&name=Logotype-3%20(1).png)
News
Sometimes it helps to know what happened, even if you can’t rewind the clock.
We’ve introduced a new feature called Block Run History, a paginated log that shows every time a block ran on a canvas. It captures the block name, execution times, statuses and timestamps down to the second.
It offers more visibility, especially in collaborative workspaces where multiple team members are iterating on the same canvas. Whether you're debugging a stubborn block or just trying to understand the block run's duration, the Block Run History helps add a bit of context.
This feature is currently live for all Zerve app users. Look for the little clock icon in the top menu.
Why we built it
- To support collaborative debugging and audit trails
- To help power users understand timing and performance patterns
- To support trust and transparency in shared spaces
We believe this new feature is a step toward helping teams understand what’s happening across their workspaces.
FAQs (Frequently Asked Questions)
What is the Block Run History feature in Zerve?
Block Run History is a new feature in the Zerve app that provides a paginated log of block executions, offering greater visibility into what happened during each run.
How does Block Run History improve collaboration?
By providing detailed run histories, Block Run History helps teams understand the sequence of events and debug issues more effectively in collaborative workspaces.
Who can access the Block Run History feature?
The Block Run History feature is currently live and available for all Zerve app users.
Why was the Block Run History feature introduced?
It was built to enhance transparency and help teams better understand the execution flow within their workflows, making debugging and collaboration easier.
Where can I find the Block Run History in the Zerve app?
Look for the new paginated log section labeled 'Block Run History' within your workspace or block details in the Zerve app interface.
Can Block Run History help with debugging stubborn blocks?
Yes, by reviewing past runs and their outcomes, users can identify issues and understand how blocks behaved during execution, aiding in debugging efforts.
