Provisioning and lifecycle
How a dedicated environment is built after payment, what happens when a step fails, and how recreation, removal, suspension and deletion work.
Provisioning starts on its own once the Dedicated subscription is confirmed. Authio builds the environment one step at a time at the hosting provider and records each step on the environment’s timeline, which the console draws as the environment assembling itself. It usually takes a few minutes.
Each step’s outcome is saved before the next one runs, so a provisioning that stops for any reason resumes from the step it was at, building on what was already created.
Environment statuses
| Status | What it means |
|---|---|
| Requested | The subscription was confirmed and the environment is waiting for its first step. |
| Provisioning | The environment is being built, one step at a time. |
| Ready | Every step ran and the API answers its health check. Only a ready environment can be changed by its owner. |
| Failed | A step kept failing and provisioning stopped. |
| Suspended | The subscription no longer covers the environment. Its services are stopped and its data is kept until the deletion date. |
| Removing | The environment is being deleted at the hosting provider. |
| Deleted | The environment and its data are gone. |
The provisioning steps
| Step | What happens |
|---|---|
| 1. Create the project | A project of its own is created at the hosting provider to hold every service of the environment. |
| 2. Create the database | The PostgreSQL service is created with its memory ceiling and the volume it keeps its data on. |
| 3. Create the cache | The Redis service is created with its memory ceiling, its volume and a password it refuses connections without. |
| 4. Create the API | The API service is created from the dedicated edition’s image, with its health check and memory ceiling. |
| 5. Create the console | The console service is created the same way. |
| 6. Assign the addresses | The API and the console get public addresses on the hosting provider’s domain. |
| 7. Platform subdomains | Where the platform has a domain for environments, the API and the console also get auth.<name>.<platform domain> and console.<name>.<platform domain>, with the DNS records they need. Skipped otherwise. |
| 8. Configure the variables | The configuration both services start with is written: connection strings, keys, addresses and the default e-mail sender. |
| 9. Deploy | The API and the console are deployed with that configuration. |
| 10. Wait until it answers | Authio waits until both deployments succeed and the API answers its health check, called from outside the way your users will reach it. |
| 11. Send the welcome e-mail | The account owner is told the environment is ready, with the console and API addresses and the user name to sign in with. |
Watching it assemble
Open Environment while it is being built. The dashboard shows each block snapping into place as its step finishes, with the time it took, and updates itself every few seconds. A step that waits on the hosting provider — the deployments, the health check — shows as waiting until the provider answers.
When a step fails
A failure at the hosting provider is usually a rate limit or a moment of unavailability, so a failed step is tried again on its own, from where it stopped. Nothing already created is deleted and built again.
| Attempt | When it runs |
|---|---|
| 1 | When the step comes up |
| 2 | 30 seconds after the first failure |
| 3 | 90 seconds after the second |
| 4 | 4.5 minutes after the third |
| 5 | 13.5 minutes after the fourth |
Wait until it answers also fails when a deployment ends as failed, crashed or removed, or when the API does not become healthy within 30 minutes.
If the fifth attempt fails too, the environment becomes Failed and provisioning stops. The console shows the step it stopped at and the error, and a platform operator resumes it from that step; when the step was the health check, the resume deploys the services again first. The page follows the progress on its own.
You do not have to wait for that: an owner or administrator of the account can recreate the environment from scratch or remove it, even while it is stuck or failed.
Recreating and removing
Both actions are in Configuration → Danger zone and ask you to type the environment’s name before they run. Neither can be undone.
| Action | What happens |
|---|---|
| Recreate from scratch | Removes the environment, then provisions a new one from the first step. The new one starts empty, with new first-access credentials, and is ready within a few minutes. |
| Remove environment | Deletes the environment’s project at the hosting provider, with its database, and removes the DNS records the platform created for it. Nothing comes in its place. |
Both delete everything the environment holds:
- The database, with every realm, client, user and their history.
- The variables you changed, such as your own e-mail server.
- Your own domain, which has to be added again on a new environment. The records at your DNS provider stay until you delete them.
Neither changes the subscription: cancel it separately if you no longer need the environment. While the subscription is active, a removed environment can be created again with Create environment at the top of the page.
Removal works on an environment that is stuck or half-built, too: whatever is already gone at the hosting provider counts as removed. If the provider does not finish, the environment stays Removing with the provider’s answer; choose Remove again, or let it be retried on its own. The account owner gets an e-mail once the environment is deleted.
Suspension and deletion
When the subscription no longer covers the Dedicated plan — it was cancelled, paused or not paid, or the account moved to another plan — the environment is suspended:
The environment is suspended
Its services are stopped and its data is kept. The account owner gets an e-mail with the date the environment will be deleted: 30 days after the suspension.
A reminder goes out
Seven days before the deletion date, the owner is reminded by e-mail.
The environment is deleted
On that date the environment and everything in it are deleted for good, and the owner gets a last e-mail.
Coming back before the deletion date
Subscribing to the Dedicated plan again before the deletion date takes the environment back: its services are started again and it returns as you left it, with the same addresses, data and settings. An environment suspended half-way through provisioning resumes from the step it was at.
After the deletion date, subscribing again creates a new, empty environment. Renewing and changing plans is covered in Plans and billing.