app_stopped
Severity: refuse. The app is stopped. The refusal's reason says why:
inactivity (no owner or admin of its organisation has been active on
Kaviris for a while) or over_cap (the organisation's free apps used their
monthly allowance).
What happened
A free app stops when no owner of its organisation, and no organisation-wide admin, has signed in to Kaviris for 30 days: the portal, the API, or an agent using their key. Visits to the app do not count. Before the stop the owners get a warning 7 days and 1 day ahead, in the portal and by email. While the app is stopped, visitors see a page saying it is paused, and its data, settings and address are kept.
With reason over_cap: the organisation's free apps used their monthly
allowance (data sent, awake time, or storage for databases and backups; see
Free beta limits), so they
are offline until the 1st of next month. Visitors see a page saying so;
nothing is lost.
Why it is refused
Resuming or deploying a stopped app is something only an owner or an organisation-wide admin can do. Signing in does not restart the app by itself: the owner chooses which apps to put back.
How to fix it
- You are an owner or an organisation-wide admin: open the app in the portal and press Put my app
back, or let your agent call
resume_app, orPOST /v1/apps/{app}/state {"state":"active"}. A deploy by an owner also puts it back. - Otherwise: ask an owner or admin of the organisation to sign in and put it back.
reasonover_cap: nobody can put it back before the new month; it comes back by itself on the 1st (the refusal says the date). The portal's Usage page shows what used the allowance. Paid plans, planned for April 2027, will keep apps running instead.
If deletion of stopped apps is switched on, get_app also says the date the
app and its data are deleted unless it is put back first.
Paid plans have no inactivity stop. See What happens to an app you stop using.