Troubleshooting Airspeed Agents

Last updated: July 13, 2026

This article covers common issues with Airspeed Agents and what to check first.

I cannot see Agents in the left navigation

Ask your Airspeed admin or Customer Success Manager to confirm Agents is enabled for your workspace and that your user account has access.

I cannot see Settings → Agents

The admin Agent Management page requires permission to view and edit organization settings. Ask an admin to check your role.

I cannot see Settings → Connections

Agent Connections may not be enabled for your workspace yet. Contact Airspeed support or your Customer Success Manager.

The Ask Airspeed bar disappears on Agents pages

This is expected. The Agents area has its own prompt and chat surfaces, so the floating Ask Airspeed bar is hidden there.

I cannot edit a template prompt

Some global or shared templates are read-only. Duplicate the agent or template first, then customize your copy.

The Variables menu is empty

Variables depend on the trigger type. Manual and scheduled agents may not have trigger-specific variables. Deal stage, after-call, and web trigger agents have different variables.

A variable did not get replaced

Check that the variable name exactly matches the Variables menu and uses double curly braces, such as {{call_title}}. If the trigger event does not have a value for that field, the inserted value may be blank.

A scheduled agent did not run

  1. Confirm the agent is active in Agents → Command Center.

  2. Check the schedule, day, and hour.

  3. Review the agent history for recent runs or errors.

  4. Confirm recipients and delivery settings are configured.

A Deal Stage Change Agent did not fire

  1. Confirm your CRM is Salesforce or HubSpot. Pipedrive CRM triggers are not currently supported.

  2. Confirm the deal moved into the selected target stage.

  3. If a previous stage is required, confirm the deal moved from that exact stage.

  4. Check whether the CRM field sync is up to date.

An After Call Agent did not fire

  1. Confirm the call has finished processing.

  2. Check whether the call has the selected tag.

  3. If the agent only runs for external calls, confirm the call was external.

  4. Review agent history for errors.

A Web Trigger Agent is too noisy

Narrow the Monitor query. Add the event type, industry, geography, company segment, or topic that matters.

A Web Trigger Agent is not firing

Broaden the Monitor query and confirm the event is likely to appear in public web sources.

Slack output is missing

  1. Confirm the Slack integration is connected for your workspace.

  2. Check whether the selected user has a matching Slack account.

  3. Confirm the channel or user was selected in Step 3: Output.

  4. For Slack channels, make sure the Airspeed app has access to the channel if required.

The output is too generic

Make the prompt more specific. Include the desired time range, data sources, criteria, output columns, evidence requirements, and recommended action format.

The output is too long

Ask for a maximum number of items, a short executive summary, or a table with specific columns.

Still need help?

Reach out to Airspeed support with the agent name, the trigger type, the expected run time or event, and a link or screenshot of the relevant agent history.