Skip to main content

Agent Setup & Scheduling

Availability times look wrong
  • Confirm the agent time zone is set correctly
  • Double-check whether you’re using 12-hour vs 24-hour format
  • Review if you applied a schedule across days accidentally
Agent changes didn’t persist
  • Ensure you clicked Save Changes
  • Refresh and re-open the agent profile to confirm

Knowledge Base

Scrape completed but AI isn’t using the content
  • Click Sync after scraping
  • Confirm the scraped content appears in files/folders
  • Try re-scraping if the URL was incorrect or incomplete
Scraping is taking too long
  • Large websites take longer than smaller ones
  • Start with the main domain (not deep links)
  • Wait and check for new structured files after completion
Content is outdated
  • Update the file manually or re-scrape your website
  • Always Sync after changes

Actions & Integrations

Integration connected but actions don’t work
  • Re-authenticate the integration (tokens can expire)
  • Confirm the correct account is connected (e.g., correct Google account)
  • Verify the action endpoint/config is correct
Action fails or returns errors
  • Check headers (Authorization key is the #1 cause)
  • Confirm endpoint URL is correct
  • Verify required arguments are provided
I don’t see my integration in the actions list
  • Confirm it was added successfully under Integrations
  • Refresh the page and check again
  • Disconnect and re-integrate if it didn’t complete authentication

Custom AI Experts and Memory

Run now is disabled for a scheduled expert
  • Confirm Schedule is selected as a trigger.
  • Turn the expert Active.
  • Save any unsaved changes.
  • Check whether the expert is marked as broken or missing required settings.
A scheduled expert did not run when expected
  • Confirm the expert is Active.
  • Review the Timezone and repeat schedule.
  • Check the Next run field after saving.
  • Make sure the schedule goal is filled in.
External trigger options are missing
  • Confirm the connected app is integrated and healthy.
  • Open External trigger settings and click Select trigger again.
  • Search by the integration or account name.
  • Reconnect the integration if its status shows unavailable.
An expert used the wrong tool
  • Open the expert and review Allowed tools.
  • Remove broad tool groups the expert does not need.
  • Save the expert and test again.
Memory content did not load
  • Refresh AI Studio > Memory.
  • Switch between Organization and User to confirm the selected scope.
  • If the page shows an error message, wait a moment and try again.
Memory changes did not save
  • Confirm the file finished loading before editing.
  • Click Save after making changes.
  • Wait for the Memory saved confirmation.
  • If the save fails, copy the intended change into a temporary note and try again after refreshing.

Abilities (Create, Edit, Triggers, Registration)

Ability doesn’t trigger
  • Trigger conditions may be too strict or not matching user phrasing
  • Confirm the interaction is happening through a supported channel (phone/email/live chat)
  • Ensure the ability is saved and active
Wrong ability triggers
  • Triggers may overlap across multiple abilities
  • Make trigger phrases more specific
  • Reduce redundancy by consolidating abilities
Registration ability keeps asking users to register
  • The user may not be recognized as registered
  • Ensure the workflow collects the right fields needed for registration
  • Verify registration logic inside the ability workflow

Building Abilities (Ask, Speak, Act, Condition)

Condition branch never runs
  • Variable name may be wrong (must match exactly)
  • Condition value may not match what users actually type (case/spacing)
  • Ask prompt may not be collecting consistent responses (add examples)
Act node creates tickets with missing details
  • Ensure your ticket instructions reference the correct variables
  • Confirm Ask nodes are connected before the Act node
  • Add optional parameters only if your workflow has those values

Best Practices for AI Studio

  • Scrape your website first, then Sync
  • Keep Knowledge Base file titles clear and specific
  • Use Condition nodes for decision points, not long prompts
  • Keep triggers specific to avoid overlap
  • Use Registration abilities only when identity matters
  • Test every branch before production use
  • Review integrated actions periodically and remove unused integrations