Skip to main content

Plan, billing and webhooks

What happens when we reach a plan limit?​

Nothing you already have stops. When adding a project, node, person or GitHub Runner would take you past your plan's limit, Jaah refuses it and says the limit is reached. When every agent is busy, a new task isn't refused: it waits, and starts as soon as a running task finishes. To see how close you are, an Org Owner or Admin opens Billing, selects the plan's name on the Plan card and reads Limits on the Subscription page. To raise a limit, free one up, select Change to pick another plan, or select Contact us to ask for a higher one.

See Check your plan and limits, Ask to change your plan and How plans and billing work.

What happens if we cancel our plan?​

You keep the plan until the end of the period you already paid for. Until then, Undo on the Subscription page takes the cancel back. On that date your organization moves to the base terms: nothing is deleted, but tasks don't start until you move to another plan. A failed payment is different: Jaah retries it while you keep the plan. Only Org Owners and Admins can cancel, from Cancel under Billing on the Subscription page.

See Change your plan and How plans and billing work.

Can we delete our organization's account?​

Yes, but only the organization's Owner can, and you can't undo it yourself. On Billing, the Owner selects the Details tab, then Delete account. The dialog says what ends: the plan ends now with no refund; nodes, hosting and running tasks stop; and everyone in the organization is signed out and can't sign back in. To confirm, type the organization's name and, with two-factor authentication, a code. To get the organization back, contact support. To stop paying but keep your work, cancel the plan instead.

See Delete your organization's account and Billing.

Can we cap what a project or group spends each month?​

Yes, with a budget, on a plan that includes Budgets. An Org Owner or Admin opens Billing › Budgets, selects Add budget, picks the project or group under Project or group, enters the cap under Monthly budget and selects Create. From 80% of the cap the budget reads Near limit. Once its spend reaches the cap, new tasks for that project or group wait; tasks already running finish. The cap lifts at the start of the next month, or as soon as you raise it.

See Set a spending budget and How plans and billing work.

What happens to a webhook when my system is down?​

Jaah keeps trying. When your system doesn't answer with a 2xx status within 10 seconds, the delivery shows Retrying and Jaah sends it again over the next day, seven attempts in all. After the last one it is Failed. Once your system is back, open the endpoint, select Deliveries and select Redeliver on the row: Jaah sends it again at once, with the same delivery id, so your system can skip one it already handled. The log keeps 30 days. A paused endpoint is different: events while it is off are never sent later.

See Receive events with webhooks and How webhooks work.

What do I do if the signing secret of a webhook leaks?​

Replace it. Open the endpoint, select the Secret tab, then Rotate, and confirm. The new secret is shown once: select Copy secret and put it in your receiver before you select Done. For 24 hours each delivery is signed with both secrets, so after a leak make your receiver accept only the new one at once. Select Send test and check the delivery reads Delivered. Org Owners and Admins can rotate, on a plan that includes webhooks.

See Replace a webhook signing secret and How webhooks work.

Do I need a new webhook when my receiver moves?​

No. Change the URL on the endpoint you have: it keeps its events, projects, signing secret and delivery log. Open the endpoint, replace the address in URL and select Save. Give the new receiver the same secret; if you no longer have it, select Rotate on the Secret tab. Then select Send test and check the delivery reads Delivered. Don't clear Enabled for the move: events that happen while an endpoint is off are never sent. A delivery that failed during the move can go again with Redeliver.

See Move a webhook to a new URL and Receive events with webhooks.

Can a webhook send only some events, or only one project's?​

Yes. Open the endpoint and, on its Settings tab, tick under Events only the events your receiver needs. Under Projects, keep All projects ticked to include every project, later ones too, or clear it and tick each project to send. Select Save. Only events that happen from then on follow the new choice; nothing earlier is sent again. To send one project's events to a different receiver, create a second endpoint for it, with its own secret and delivery log.

See Change which events a webhook sends and How webhooks work.