Skip to content

Projects Troubleshooting & Gotchas

These are the things that most often catch people out when they’re new to Projects, and what to do about each one. If your problem isn’t covered here, contact hello@jetstack.ai.

Projects is in limited release and isn’t turned on by default. Check these:

  • Your organisation doesn’t have access yet. Email hello@jetstack.ai from the address you sign in with, and include your organisation name. See Getting Access.
  • You’re in a different organisation. Switch organisations using the selector in the top-left of the dashboard (or at the top of the extension).
  • Your browser is showing an old page. Hard-refresh the dashboard (Cmd/Ctrl-Shift-R), or close and reopen the extension.

Projects shows in the dashboard but not in the extension

Section titled “Projects shows in the dashboard but not in the extension”

In the extension, switch to another organisation and back again.

Jetty says it can’t see some of the portal

Section titled “Jetty says it can’t see some of the portal”

Jetty won’t guess about parts of the portal it hasn’t scanned yet, so it doesn’t create duplicates by mistake. Check the Portal data card on the Overview page:

  • HubSpot API scan runs by itself.
  • Extension scan needs the client’s portal open in Chrome with the extension signed in.

Then approve Jetty’s rescan card, or click Run scan on the Portal data card.

Assets I know exist are missing from the Canvas

Section titled “Assets I know exist are missing from the Canvas”

Check when the portal was last scanned (Last read on the Portal data card). If the client’s team has made changes since, scan again.

Jetty described a change but nothing happened

Section titled “Jetty described a change but nothing happened”

Jetty can’t change anything without your click. Look for the card in its reply and press the button. If there isn’t one, ask for it: “put that on a plan” or “let’s deploy”.

What happenedWhyWhat to do
The deploy card changedSomething on the card changed after it was sentAsk Jetty for a new deploy card
Nothing is readyNothing on the card can be deployed right nowRead the reasons on the card and deal with them
The portal is disconnectedThe portal’s connection to JetStack AI has expiredReconnect the portal under Client Accounts, then try again
The confirmation didn’t matchThe word you typed on a remove card doesn’t matchType exactly what the card asks for

A card marked Replaced by a newer card can’t be used any more. Use the newest one.

Something from my document isn’t on the plan

Section titled “Something from my document isn’t on the plan”

First check the You do this steps. Things Jetty can’t build are listed there with instructions (see Things You’ll Always Do Yourself). If something is still missing, ask: “what from the spec isn’t on this plan?”

Jetty asks about something I already told it

Section titled “Jetty asks about something I already told it”

Answers on a questions card are saved automatically. If you answered in a normal message instead, say “add that to the project knowledge” so Jetty remembers it for every later plan.

It never reached HubSpot, so nothing needs cleaning up. Ask Jetty to try again. It adds the asset to a new plan, and anything that was already built stays as it is.

An asset says “Couldn’t build · you do this”

Section titled “An asset says “Couldn’t build · you do this””

Jetty couldn’t build it, so it became a step for you with instructions. Follow them, or ask Jetty whether there’s another way to build it.

Look for Add credits to resume. When your Projects credits run out, the build pauses instead of failing. Add credits and it carries on where it stopped.

These assets need the Chrome extension. Open the client’s portal in Chrome with the extension signed in, go to Projects → Inbox, and click Start. If the same deploy also has assets that go live right away, those go first, so the Start button may need a moment.

The inbox only shows work for the portal you have open. Check that the portal ID in your HubSpot address is the client’s portal. If the extension says “Open a HubSpot portal”, go to any HubSpot page for that portal and refresh the extension.

The receipt shows HubSpot’s exact message. Click Fix and deploy on the fix card Jetty sends. If the asset needs the Chrome extension, ask Jetty to deploy again after the fix.

It went live, but it needs a finishing step from you in HubSpot. For example, a workflow might need a real owner before you switch it on. Open the asset to see the Setup remaining steps. See Setup Remaining.

Workflows are always created switched off. Check the enrollment settings and any setup steps, then switch the workflow on in HubSpot.

Someone edited it in HubSpot after it was deployed. Click Keep HubSpot’s version on the fix card to accept their change, or ask Jetty to change it back.

  • Use the Open in HubSpot link on the receipt.
  • Dashboards and reports belong to the HubSpot user who deployed them through the extension. If the plan didn’t include sharing, check their sharing settings in HubSpot.
  • Marketing emails and some other assets need the right HubSpot subscription on the portal.

Chatting and building use your organisation’s Projects credits. If you run out, Jetty keeps your message and marks it Not answered — not enough Projects credits, and any build in progress pauses until you add more. You can check your balance in your organisation’s billing settings.

  1. Copy the page address of the chat. It includes the project and the chat.
  2. Note the time the problem happened.
  3. Take a screenshot of the card, receipt or error.
  4. Email hello@jetstack.ai with the above and a short description of what you expected and what happened.