Skip to content

Return grace period state from the API #8256

Closed

Description

@talissoncosta

Two booleans per organisation, on the response the usage page already fetches:

  • has the paid grace period been used? False means this month is covered, true means overage is charged. The page has to say which
  • can this organisation be cut off? Restriction is switched on per organisation and some are exempt

Careful: the grace record is also written on the free path today, so it can be true for organisations that never used anything. Untangle that first or the page will tell customers they are being charged when they are not.

Done when a paid organisation over its limit can be told whether it is covered or charged.

Activity

  1. changed the title [-]Expose grace period state with usage data[/-] [+]Return grace period state from the API[/+] on Aug 11, 2026
  2. talissoncosta commented on Sep 3, 2026

    @talissoncosta
    ContributorAuthor

    One more field the frontend needs from this: stop_serving_flags.

    It's on the model but on no serializer, so the dashboard can't tell whether flag serving actually stopped. block_access_to_admin is exposed, so we can say an organisation is restricted, just not what is paused, and those two are independent switches.

    That's the blocked half of #8187: without it the usage page shows a restricted organisation the same generic over-limit copy as anyone else.

  3. 5 remaining items

  4. added 4 commits that reference this issue on Sep 23, 2026
    a5ba5f3
    f6bae67
    8142f2f
    77b5ea2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

apiIssue related to the REST API

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions