Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

4.2. Artifacts and Logs

💡 First Principle: Every run leaves two kinds of evidence — logs, which the platform captures automatically, and artifacts, which the workflow chose to keep — and both are reachable through the same two surfaces, the web UI and the REST API, with the API being the answer whenever a scenario mentions automation or scale.

Why care: at one repository the UI is fine. Across an enterprise, questions like "which workflows produced artifacts over 1 GB last month?" or "delete all artifacts older than 14 days to reclaim storage" are only answerable programmatically, and the exam tests whether you know the endpoints exist and what they return.

⚠️ Common Misconception: "Artifact retention and log retention are one setting." They share a default (90 days for public repositories, configurable at enterprise, organization, and repository level), but artifacts can additionally be shortened per upload with retention-days, and artifacts can be deleted individually via API or UI while logs are deleted as a run's whole archive. Storage billing tracks artifacts and packages, not logs.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder18 professional certifications