Hey, could someone check why the customer’s setup failed?
You shouldn’t need a ticket for this.
Ask what happened. See your pipelines. Get work moving.
Less busy work.
More progress.
Found the failed step. Ready to retry?
Product demo
Simulated approval · Dana Okafor, Manager
Scene 4 of 4: Resolve
Your stack, in the conversation.
- Internal APIs — Approved business actions
- PostgreSQL — Operational records
- MySQL — Operational records
- MariaDB — Operational records
- SQL Server — Operational records
- Oracle — Operational records
- CockroachDB — Operational records
- MongoDB — Documents
- ClickHouse — Analytics
- GitHub — Issues, pull requests and workflows
- Snowflake — Analytics
- BigQuery — Analytics
- Redshift — Analytics
- Slack — Questions and updates
- Jira — Tickets
- Gmail — Drafts and communication
- Microsoft 365 — Drafts and communication
- Notion — Pages and notes
- HubSpot — Contacts, companies and deals
- Stripe — Customers, invoices and subscriptions
- GitLab — Pipelines
- Supabase — Managed PostgreSQL
- Neon — Managed PostgreSQL
- Aurora PostgreSQL — Managed PostgreSQL
Tell #northline-launch the setup is fixed.GlowFormHere is the message. It posts as you, once you say so.# northline-launch
Northline’s setup is fixed — provisioning timed out on capacity, the retry finished in 3m 12s, and they are live as of 10:31 AM.
Send to #northline-launch Posts as you
- Draft an update to Priya at Northline.GlowFormDrafted from the action receipt. Nothing leaves until you send it.
- To
- Priya Raman
- Subject
- Your workspace is ready
Hi Priya — a provisioning step timed out this morning and held up your setup. It has been re-run and all 250 seats are live…
Send email Sends as you
Open a ticket for the capacity timeout.GlowFormReady to file with Platform, job log attached.New ticket · Platform
Capacity timeouts in us-east-1 during provisioning
- Priority
- High
- Attached
- Job log · #4821
File ticket Goes to Platform
Which setup stage failed most this month?GlowFormProvisioning, by a distance: 9 of 14 failures, all of them capacity timeouts in us-east-1.Failed setups by stage · this month
Why are setups failing?GlowFormMostly capacity. Nine of this month’s 14 failures were timeouts waiting for it.- Capacity timeout 9
- Seat mismatch 3
- Billing hold 2
- Are setups getting faster?GlowFormYes. The median is down to 6m 40s, from 11m 12s eight weeks ago.
Median setup time · last 8 weeks 6m 40s
↓ 4m 32s vs eight weeks ago
Provision agent guardrails to safely assist any enterprise persona.
Sam, Sales. Allowed: read records, chart the numbers, draft emails, post to slack. Needs approval: issue refunds. Blocked: retry in production, connect systems, publish access, approve requests, delete records.
Set Northline’s primary contact to Priya Raman.GlowFormThat is one row in customers. It updates when you say so.customers · 1 row · cus_8241
Primary contact
Alex Chenchanges to Priya RamanUpdate row Writes to customers as you
Re-run provisioning for Northline.GlowFormThat is a published operation. It can only touch the customer you name.Operation · Retry provisioning
POST /internal/provisioning/retry
- Customer
- cus_8241
- Job
- #4821
Request approval A manager approves this operation
Pause the nightly sync until capacity is back.GlowFormDone when you confirm — it holds one pipeline and nothing downstream of it.Pipeline · Nightly sync
State
Runningchanges to PausedPause sync You own this pipeline
- How many setups are blocked right now?GlowFormThree of today’s 41 runs.
3 of 41 runs
- Northline RoboticsProvisioning
- Vertex LabsValidated
- Northwind FreightProvisioning
- Show me Northline’s record.GlowFormHere it is. You can read this table; changes go through an admin.
customers · cus_8241
- Name
- Northline Robotics
- Plan
- Enterprise · 250 seats
- Region
- us-east-1
Delete Northline’s customer record.GlowFormOperations cannot delete customer records. An admin can — I can draft the request for one.Not permitted for Operations
Less back-and-forth. More handled.
Give your team a clearer path from questions to action.