Skip to content

Document lambda error behaviour when wrapped with Laconia #626

Open
@Ankcorn

Description

It would be really helpful if Laconia had some documentation on how errors should be handled. I know the apiAdapter has some support for this but for other triggers, the way errors should be handled differs. For example, SQS will retry the message so you should let exceptions bubble up.

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions