Skip to content

Sablier services don't expire unless accessed via their URL #713

Description

@nickshanks347

I have several Docker stacks running, including Sablier. When I start everything with docker compose up -d, the stacks that are managed by Sablier remain active even after their configured session duration has passed.

It seems that Sablier only detects and expires these services after I manually visit their URLs - at which point it “discovers” them and correctly terminates the sessions after the specified duration.

Is this the intended behavior, or am I missing a configuration step?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions