What a plan limits, what it never limits, and what happens over a limit

An organization of Slen is on one plan: Free, Pro, Team or an individual plan. The plan decides how much the organization can set up — projects, published flows, members — and how much history of its executions it keeps. It never decides whether a request is served. This page says what a plan limits and what happens when you reach a limit.

What a plan never limits

The protection of your money is the same on every plan, Free included:

• budgets, policies and the hold every request takes before a model is called;

• the overrun policy of a model node — except one that asks a person for an approval, which is part of approvals;

• the cache of answers and following executions on the canvas as they run;

• the SDKs and the API: a request to a flow is never refused because of a plan.

Limits close creating, never running

A limit of a plan closes creating and changing, never running. When the organization reaches one, it cannot create or publish one more of that thing; everything already set up keeps serving requests.

• A request to a flow is never refused for a plan: not over a limit, not after a move to a smaller plan.

• A refusal comes when you create, publish, invite or change something the plan has no room for. The console says which limit was reached and which plan has room for more; the API answers with an error code of its own — Error codes.

• Deleting, archiving, pausing, blocking and reading are never closed.

What the plans limit

Some features come with a plan as a whole:

On Free an organization has one project and one published flow, keeps no customers and invites nobody: it is one person. That person can still join the organization of someone else, whose plan pays for the seat.

The numbers of each plan and the prices are on the pricing page. The plan page of the console's settings shows the numbers of your organization and how much of each is used.

Executions with history

An execution is counted once, when it reaches a model or the cache. An execution refused before that — by a budget, a policy or the credits of a customer — is not counted, and neither are the retries and the switches to another connection inside one execution, the reads and the management API. The count starts again on the first day of every month, by UTC.

When the executions of the month pass the quota of the plan, the history pauses. New executions keep running with every protection of money: their holds, their budgets and the ledger are written, and their traces are not. Such an execution is marked in the list of executions and has no trace. The history resumes on the first day of the next month, or at once when the organization moves to a bigger plan.

How long the history is kept

The history of executions — the executions, their traces, the requests and the attempts — is shown for the period of the plan. An execution older than that is hidden at once and deleted 30 days later; within those 30 days a bigger plan shows it again. The ledger, the holds and the credits of customers are kept whatever the plan.

Move to a smaller plan

Nothing is deleted at the moment an organization moves to a smaller plan, and nothing stops serving requests. What is over the new limits stays as it is and cannot grow:

To get back within a limit, archive or delete what is over it: for published flows, archive the ones you do not need. The owner of the organization chooses which members stay — suspends one and brings back another.

An individual plan

A bigger organization gets an individual plan: it starts from Team, and any limit or feature is set apart for the organization — more executions, a longer history, up to a year, more seats or projects. Any plan can carry such a setting: Pro with more published flows, for example. The plan page of the console marks every limit set this way.

Buy, change or cancel a plan

Only an owner of the organization buys a plan and changes it; the other members see the plans and are told to ask an owner. In the console, open the plan page of the settings and choose Compare plans: the plans page marks the current plan and offers the others, paid monthly or yearly.

• Buy. From Free, choose Pro or Team; for Team, choose how many seats to add to the ones it includes. The payment opens over the console; once it goes through, the plan changes within a minute. Your email address must be confirmed first.

• Change. A higher plan, more seats or yearly payment takes effect at once, and the difference for the rest of the period is charged at once. A lower plan, fewer seats or monthly payment takes effect at once too, and the difference for the rest of the period is refunded at once to the card you paid with. Before you confirm, the console says what is charged now, what is refunded and when the next payment is — and which members a smaller number of seats suspends. When a change cannot be counted right now — on the day the subscription renews, for example — the console says so: try again after the renewal, or write to support@slen.ai.

• Cancel, the card and the invoices. They are in the customer portal of FastSpring, our Merchant of Record — Payments and invoices on the plan page opens it, for the owner who started the subscription. A cancellation takes effect at the end of the paid period, and the organization then moves to Free — see Move to a smaller plan. Until then a cancellation can be taken back: Keep subscription.

• A payment that failed. The plan stays while the payment is tried again, and the console asks to update the card. A payment that never goes through ends the subscription, and the organization moves to Free.

Prices are in US dollars and shown without taxes, which FastSpring adds when you pay. An individual plan, or a plan set apart for the organization, is not bought in the console: write to support@slen.ai from the address of your account and name the organization. The plans and their prices are on the pricing page; refunds follow the Refund policy.

Where to go next

• Organizations, projects and roles — what an organization and its members are.

• Inspect an execution — the list of executions and their traces.

• Customer credits — the credits of your customers, on Pro and above.

• Error codes — every code of the API, what it means and what to do about it.