Skip to content

E4: Failure Notification — Rich Detail #28

@ShortCipher5

Description

@ShortCipher5

Failure notifications must carry enough detail for developers to diagnose issues without opening multiple screens.

References: PRD §6.5

Acceptance Criteria

  • Shows: which step failed (e.g. "Build - step 2 of 8")
  • Last 20 lines of log output from failed step with "View full logs" link
  • Whether rollback was attempted and its outcome
  • Plain-language AI suggestion for recognised failure patterns (missing env var, OOM during build, health check path returning 404)
  • Detail surfaced in both in-app tray AND external channel payload

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions