My run failed#
Open the run in Runs to see the reason. Common causes: HubSpot needs a reconnect, a permission (scope) is missing, the record was deleted in HubSpot, HubSpot was busy, or a temporary error. Failed runs are not charged and do not cost credits, so you can simply run it again once the cause is fixed. If it fails again with the same message, ask for a person in the support chat and mention the run.
"This run reached its limit of AI calls" or "its AI token budget"#
Every run has a fixed safety limit on how much AI work it may do, so one unusual record can never run away with cost. A run that hits it stops and is marked Failed with "This run reached its limit of AI calls." or "This run reached its AI token budget." The run is not charged: failed runs are free and any credits are returned. Normal runs stay far below the limit, so this usually means the record or the custom agent's instructions are unusually large. Running it again on the same record gives the same result; try a smaller segment or shorter custom agent instructions, or ask for a person in the support chat and mention the run.
"Analysis creation failed" when starting a run#
The run could not be created, and nothing was charged. Click Retry. If the message says to reconnect HubSpot or that the connection is not authorised (for example to read tickets), an owner or admin must reconnect HubSpot on Integrations first. If it says you are out of credits, see "What happens when I run out of credits".
"We couldn't reach HubSpot just now"#
A run (or a run you were starting) failed with "We couldn't reach HubSpot just now. The run wasn't charged — please try again in a few minutes." This is a temporary problem talking to HubSpot, on HubSpot's side (down or busy) or ours. Your HubSpot connection is fine: there is nothing to reconnect, and the run was not charged. Wait a few minutes and run the agent again. If it keeps happening for more than an hour, check the status page and ask for a person in the support chat. Only the message "HubSpot token refresh failed. Reconnect HubSpot or verify OAuth credentials." (or the red "access was revoked" banner) means an owner or admin must reconnect HubSpot on Integrations.
HubSpot rate limits and "HubSpot is busy" errors#
HubSpot limits how many requests an app may send per portal. Alignify paces its requests and retries temporary HubSpot errors automatically. If HubSpot still refuses (for example during a large scheduled scan or when other apps use the same portal heavily), the run fails at no cost or a WriteBack shows "HubSpot rate limit reached … Retry later". Wait a few minutes, then run again or click Retry apply.
The report is empty or says there is not enough data#
Agents only use what is logged in HubSpot. A new deal with no activity, a contact without emails or calls, or fields left empty give thin reports, and the report lists what was missing. Log the calls and emails in HubSpot (or connect your inbox to HubSpot), fill in key deal fields, and run again, at Deep depth for long histories. If the report says some data "could not be read", see the missing permissions answers.
"This deal is closed": why an agent will not run on a closed deal#
Pipeline Risk, Stale Deals, Discovery Prep and Deal Template Analysis work on open deals. When you pick a deal that HubSpot marks closed (won or lost, including closed stages of your own pipelines), the run form says so, the run is refused with "This deal is closed" and no credits are charged. Use Closed-Won Analysis for a won deal and Closed-Lost Analysis for a lost one. Scheduled and HubSpot-triggered runs skip closed deals the same way, for free.
Does the agent use the company's or contact's history when the deal has none?#
Yes. When a deal has fewer than three logged activities of its own (common for renewals and repeat deals), the agent also reads up to 20 of the most recent emails, calls, meetings and notes of the deal's company and its first two contacts. The report treats them as related company/contact activity: background about the account, never as activity on the deal itself, so they do not change days since last activity or staleness.
The report says some activities could not be read#
HubSpot refused part of the record, usually because the connection is missing a permission such as sales email reading. The agent says what it could not read and keeps its conclusions cautious. An owner or admin can reconnect HubSpot to grant the missing permission.
The agent cannot find my deal or contact#
The record picker searches HubSpot live. Check that you are in the right workspace, that the record exists in the connected HubSpot portal, and that the HubSpot connection is healthy on Integrations. Newly created records can take a minute to appear in HubSpot search. Search by the record's name as shown in HubSpot.
A schedule did not run#
Check Schedules: the schedule may be paused (with the reason shown), the workspace may be out of credits (runs are skipped until credits are available), or HubSpot may need a reconnect. Times are in UTC, so a "09:00" schedule runs at 09:00 UTC. Event schedules run only when a deal in the chosen pipeline and stage changes in HubSpot. A time schedule over a segment with no matching deals or contacts runs nothing. Check Runs for runs started by the schedule.
"Monthly usage limit" although I still have credits#
In rare cases of very heavy use a run can be refused with a message about the plan's monthly usage limit even though credits remain. Ask for a person in the support chat; we will look at your workspace.
I can't log in or sign in#
Sign in at the sign-in page with the same method and email you used to sign up (sign-in is provided by our sign-in service, Clerk): if you signed up with Google, click Continue with Google. Use "Forgot password" on the sign-in form if you signed up with a password, and check spam for sign-in codes: a password sign-in on a new device or browser asks for a code we email you. Make sure cookies are allowed for the site, and try a private window to rule out extensions. If you were invited, sign in with the exact email the invite was sent to. If you still cannot get in, write to contact@alignifytech.com from your account email.
Buttons are disabled: I cannot run agents, change billing, schedules or HubSpot settings#
Members have view-only access: they can see Runs, reports, WriteBacks, Schedules, Usage and Activity, but running agents, billing, schedules, the HubSpot connection, approvals, custom agents, playbooks and team management are for owners and admins. Disabled buttons say "Only workspace admins can do this. Ask a workspace admin." Ask an owner or admin of your workspace to make the change, or to make you an admin in Team. Also check the workspace switcher: you may be in a different workspace where you have another role.
Which browsers are supported?#
Alignify is a web app; use a current version of Chrome, Edge, Firefox or Safari on desktop for the best experience. Pages also work on phone screens. Very old browsers and Internet Explorer are not supported. Allow cookies for sign-in.
The app looks out of date or a button does nothing#
Refresh the page. If you use several workspaces, check the workspace switcher in the top bar. A disabled button usually shows why when you hover it (often your role, "Only workspace admins can do this", or a missing approval). If it persists, ask for a person in the support chat with a short description of what you clicked.