Logs, versions, and improvement

Inspect runtime results, audit releases, and improve integrations from production evidence.

  • Logs: Execution logs for debugging. Filter by status (Success/Failed), date, or trigger.
  • Operational transparency: Understand who changed what, when it changed, and why—especially via promotion history.

Improve#

Learn from production and evolve architecture without restarting the foundation.

Version history and auditing#

Every promotion creates an immutable version snapshot.

  • The log: Open History to see a timeline of deployed versions.
  • Attribution: See who deployed a version, when, and the associated commit ID.
  • Accountability: Audit trail for compliance and incident analysis.

Documentation and mocking#

  • Documentation: Projects and gateways can generate documentation for workflows and published APIs.
  • Mocking: Test workflows with mock data before connecting live services.

Reuse and iteration#

  • Refine workflows in development without affecting production traffic.
  • Extract shared logic into functions.
  • Swap connectors when vendors change while keeping workflow structure.
  • Use production learnings—logs, failures, usage—to improve the next promotion.