Troubleshoot Agent Runs – Jasper Success Center

Use this guide when an Agent doesn't run, stops early, or returns something unexpected. Check status.jasper.ai first for widespread issues.

Error Messages and Resolutions

Error message	What to do
Failed to create your agent. Please try again.	Try again. If it repeats, shorten the request or remove the example.
Creating your agent is taking longer than expected. Please try again.	Try again in a few minutes.
Sorry we can't access the example you provided.	The page may be private. Paste the text or upload the file.
Add at least one input field to test this Agent	Add an input under Input fields, then test.
Instructions must not be empty	Add instructions before saving.
Please fix the invalid mentions	An @ reference points to an input, Knowledge item, Agent, or connector that no longer exists. Remove or replace it.
Failed to generate content. Please try again.	Run the test again. If it repeats, see The run stops or fails below.
Could not open a new tab. Please allow pop-ups and try again.	Allow pop-ups for Jasper to use Test in Canvas.
We couldn't start this Task Agent. Please try again.	Refresh and run again.
Failed to set active version. Refresh and try again.	Refresh the page, then make the version active again.
One or more saved settings are no longer available. Review the selection before saving this version.	A Brand Voice, Audience, Style Guide, Knowledge item, or Product in the Agent's Jasper IQ settings was deleted, or you no longer have access to it. Pick a replacement, then save the version.

In Canvas, open the activity panel to see the run status: Completed, Failed, or Cancelled.
Large runs with many documents, long research, or several subagents can take longer. Let the run finish before running again.
If an orchestrator fails, test each subagent on its own to find the step that breaks.

The launch email came back without the legal disclaimer. Keep the approved text in Knowledge, attach it, and add a step such as “Close with the disclaimer from @Approved disclaimers, word for word.” Repeat it in the output section. If a subagent writes the email, add the step to that subagent.
It ignored our channel specs. Number the steps and put hard rules, such as character limits, in a “Rules” line.
The sales one-pager at the end is cut off. Ask for fewer documents per run or split the work across subagents.
The whole launch kit came back as one document. Ask for each asset as its own titled document.
It doesn't sound like us. Check the Brand Voice and Style Guide in the Agent's Jasper IQ settings and in the Jasper IQ section of the run. Remove tone rules in the instructions that contradict them, and update Example output.
It ignored our brand rules or used a banned word. Check that the right Style Guide is attached. Add the rule to the Style Guide instead of the instructions, so every Agent that uses it follows.
The brand check didn't run. Reference the checker subagent with @ in the instructions and say when to call it.

My regional team can't see the Agent. Set Access to Anyone in your workspace. If you can't publish, ask your Admin about publishing permissions.
Another team gets different results, or it fails for them. Check which version is active, and that subagents and Knowledge are shared with the workspace. The Agent's Jasper IQ settings are defaults, so check whether that team picked a different Brand Voice, Audience, or Style Guide in the Jasper IQ section of their run.