Keep building block runs for deleted building blocks
complete
Felix
For troubleshooting purposes I need to be able to figure out which building block run was running when and which output it produced.
Right now, building block runs are deleted once the building block is deleted.
Recently I forgot to add terraform state to my building block and all deletions went through succesfully, however the instances stayed there. Took me a long time to figure out what I did wrong. It would have helped immensely if I could have seen the deletion logs.
Jelle den Burger
updated the status to
complete
Soft-deleted Building Blocks and Runs now available
As of meshStack v2026.21.0, building blocks and their runs are no longer permanently deleted — they are soft-deleted and remain accessible for audit and troubleshooting.
What's available now:
- Deleted building blocks remain visible with their full run history
- The meshObject API now supports filtering by lifecycle state — you can query soft-deleted building blocks explicitly using the lifecycleState filter
- The deletedOn field is exposed in lifecycle metadata
- Default API behavior is backward compatible — only active building blocks returned unless you request deleted ones
- Important: Building block deletion requires Terraform provider v0.20.9 or later to work correctly
See the public API documentation for details on the lifecycle filter.
Janny the AI Product Manager
We are actively working on this.
meshStack v2026.20.0 included internal changes to soft-delete building blocks and their runs rather than permanently removing them. This is the foundation that makes it possible to keep run history accessible after a building block is deleted.
What's coming in upcoming releases:
- Deleted building block runs will remain visible in the UI for troubleshooting
- Run logs and outputs will be accessible after deletion
- Full deletion history will be preserved so you can trace what happened during a run
Note for API and Terraform users:
This is a breaking change for consumers of the BuildingBlock v2-preview API. Currently, fetching a deleted building block returns a 404. After this change, the resource will still be returned - you will need to check the status.lifecycle
field to determine if a building block has been deleted. This change will also impact the Terraform provider. We will provide detailed migration instructions once these changes ship.We'll update this post once the feature is live. Thanks for your patience!
Janny the AI Product Manager
updated the status to
in progress
J
Julia Rengshausen
Please make this a feature! The logs don't even need to be there for a long time. Even just 5 minutes would be enough for troubleshooting.
Jelle den Burger
Thank you for your request! It makes a lot of sense to have this and we will keep it mind for the future.