Projects Troubleshooting & Gotchas
This page is the field-tested list of things that surprise people the first few times they use Projects, and what to do about each one. If you hit something that is not covered here, contact hello@jetstack.ai — we add patterns to this page as we see them.
Access and Visibility
Section titled “Access and Visibility”I don’t see the Projects tab
Section titled “I don’t see the Projects tab”Projects is in limited release and is disabled by default. Three things can be true:
- Your organisation is not enabled. Email hello@jetstack.ai from your sign-in address with your organisation name. See Getting Access for the full request flow.
- You are signed into the wrong organisation. If your account has multiple workspaces and only one is enabled, switch using the workspace selector in the top-left of the dashboard (or the header in the extension).
- Your browser cached the previous state. Hard-refresh (Cmd/Ctrl-Shift-R) the dashboard or close and reopen the extension. The gate is read on first organisation load.
I had access yesterday but the tab is gone now
Section titled “I had access yesterday but the tab is gone now”Limited-release organisations can be temporarily flagged off during incident response or a rollback. Existing projects are not deleted — they reappear when access is restored. Contact us if you need confirmation or an ETA.
The dashboard shows Projects but the extension doesn’t
Section titled “The dashboard shows Projects but the extension doesn’t”The extension checks for access when it loads and when you switch organisations. If the two surfaces disagree, the extension is showing a cached state. Fix: in the extension, switch organisations and switch back.
Portal Setup and the Canvas
Section titled “Portal Setup and the Canvas”The Canvas shows “not scanned yet” for some domains
Section titled “The Canvas shows “not scanned yet” for some domains”That is by design, not an error. Domains scanned by the browser lane (dashboards, reports, snippets, and other in-portal-only types) need the Chrome extension to run with an active session on the client’s portal. Open the extension on that portal and follow the Finish scan in HubSpot prompt in its inbox. The Canvas deliberately never renders “we haven’t looked” as a zero — an unscanned domain says so.
A rescan seems to only half-finish
Section titled “A rescan seems to only half-finish”A rescan runs both lanes, and they progress separately. The API lane completes on its own; the browser lane waits for you to finish it through the extension. Check the extension inbox for the pending scan before assuming the rescan is stuck.
The Canvas is missing assets I know exist
Section titled “The Canvas is missing assets I know exist”- Check the mode. Sandbox and production are separate portals with separate Canvases — you may be looking at the other one.
- Check the domain’s last-scanned time (shown per lane). If the client’s team has been busy since, rescan.
Project Knowledge
Section titled “Project Knowledge”An uploaded document is not becoming knowledge
Section titled “An uploaded document is not becoming knowledge”After attaching a file via the paperclip, make sure you send the message — until then, the document is staged, not uploaded. Once sent, the document appears in the Documents library with its analysis state. If analysis fails, the usual causes are an oversized file or an unsupported format — re-export to PDF/DOCX/TXT/Markdown and try again.
Jetty won’t act on something I told it
Section titled “Jetty won’t act on something I told it”If the statement never became published knowledge, Jetty treats it as conversation, not fact. Ask Jetty to capture it (“add that to the project knowledge”) — chat-captured claims are published with your own message as their cited source. If the claim conflicts with another source, it lands in the Knowledge review queue and needs your resolution.
Blueprint
Section titled “Blueprint”The Blueprint says “Update available”
Section titled “The Blueprint says “Update available””The brief has changed since the current Blueprint version was derived. Nothing is wrong — trigger the update when you want the design brought current. Releases planned against the older version keep their pinned design until you re-plan them.
The Blueprint feels generic
Section titled “The Blueprint feels generic”Generic design means a thin brief. Resolve open decisions and conflicts in the Knowledge review, add real sources (a transcript, a process doc), and re-derive. A single concrete example — “we lose deals when SDRs forget to log demo no-shows” — reshapes an entire section of the design.
Releases and Generation
Section titled “Releases and Generation”A requirement I discussed isn’t in the Changes tab
Section titled “A requirement I discussed isn’t in the Changes tab”Check its disposition. Every accepted requirement is persisted in the plan, including ones that cannot be executed automatically — those stay listed with the reason (manual step needed, not automatable, needs a decision) rather than turning into silent omissions. If the requirement is missing entirely, it never made it into published knowledge — see the Project Knowledge section above.
Generation paused mid-run
Section titled “Generation paused mid-run”Look for a credits notice: when a run exhausts your organisation’s AI credit balance, it pauses instead of failing. Top up credits and the same run resumes where it stopped — nothing regenerates from scratch and nothing is lost.
Generation seems stuck
Section titled “Generation seems stuck”Generation runs in the background and larger Releases legitimately take a while. If a Release’s generation has not advanced for a long stretch and there is no credits notice, cancel it from the Release and re-run — completed specs are kept. If it happens repeatedly on the same Release, contact us with the project ID.
A single asset keeps generating wrong
Section titled “A single asset keeps generating wrong”Regenerate just that asset from its detail view rather than re-running the Release. If it keeps coming out wrong, the cause is almost always upstream: a thin or conflicting spot in the brief or Blueprint that this asset depends on. Ask in the Release chat — “why does the lead-routing workflow keep coming out wrong?” — Jetty can see the generation history and usually points at the root cause.
Deployment and Verification
Section titled “Deployment and Verification”The extension says there’s nothing to apply, but the dashboard disagrees
Section titled “The extension says there’s nothing to apply, but the dashboard disagrees”The extension only shows pending work for the portal it is open on. Confirm you are in the portal bound to the Release’s active mode — sandbox and production are different portals. Switch portals in HubSpot and the pending apply appears.
An asset failed to apply
Section titled “An asset failed to apply”Open its row in the Delivery tab and read the verbatim HubSpot outcome — it is the real error, not a paraphrase. Then use Repair on that asset: the failure is classified and routed to the right fix, the single asset redeploys, and previously blocked dependents unblock. See Repair, Not Restart for the common patterns table.
An asset says applied but I can’t find it in HubSpot
Section titled “An asset says applied but I can’t find it in HubSpot”- Wrong portal or wrong mode — the most common cause. Check which portal the active mode is bound to.
- Scoping — dashboards, reports, and CRM cards are created in the applying user’s scope; share them in HubSpot for the client team.
- Hub requirements — marketing emails and similar assets need the destination portal’s Marketing Hub active.
If none of those apply, check the asset’s verification result — verification reads the portal back after apply, and an asset that truly is not there will have failed it rather than showing healthy.
Verification flagged an asset as not matching its spec
Section titled “Verification flagged an asset as not matching its spec”Someone (or something) changed it portal-side, or the apply landed partially. The row shows exactly which fields mismatch. Repair re-applies the spec in place. If the portal-side change was intentional — the client’s admin customised it — leave it; verification is information, not enforcement.
AI Credits and Pricing
Section titled “AI Credits and Pricing”Projects generation and AI-driven planning consume org-level AI credits. Runs that hit an empty balance pause and resume rather than failing (see above). Balance and usage are in your organisation’s billing settings. During limited release there is no separate Projects SKU — asset entitlements follow your existing plan, and any pricing changes at general availability will be communicated in advance.
Reporting an Issue
Section titled “Reporting an Issue”If you hit a failure that is not covered here, or a behaviour that does not match this documentation:
- Capture the project ID from the URL of the project workspace (and the Release ID if the issue is inside a Release).
- Note the time — we use this to find the relevant log entries.
- Take a screenshot of the error message or the unexpected state.
- Email hello@jetstack.ai with the above and a short description of what you expected vs what happened.
Issues that include a project ID and a timestamp are usually resolved within one business day.
Next Steps
Section titled “Next Steps”- Projects Overview — The workspace end to end
- Getting Access — Limited-release request flow
- Quickstart — First project walkthrough