This article addresses the **request failed: 400** error that can appear in Atlas Agent when submitting a hero image prompt. A 400 error means the request was rejected before it was processed.

Before reaching out to our team, try the self-serve steps below — many users are able to resolve this by adjusting their prompt.

## **🔧 Self-Serve Steps to Try First**

1. **Retry the prompt:** Occasionally a transient issue can cause a 400 error. Submit the exact same prompt again to see if it succeeds on a second attempt.
2. **Simplify the prompt:** Shorten your hero image prompt to the core description, removing any extra instructions, punctuation, or formatting. A very long or complex prompt can sometimes trigger a rejection.
3. **Check for unsupported characters:** Remove any special characters (e.g., **/**, **&**, **<**, **>**, quotes within quotes) from the prompt text and try again.
4. **Try a different prompt entirely:** Write a new, plain-language description of the hero image you need. If this succeeds, the issue is specific to something in your original prompt wording.
5. **Reload the page and try again:** Refresh your browser, navigate back to the Atlas Agent project, and resubmit the prompt to rule out a session-level issue.

## **📋 If the Error Persists — What to Prepare Before Reaching Out**

If none of the steps above resolve the error, our team will need to investigate on a case-by-case basis. Please have the following ready:

- **Your project name:** The exact name of the project where the error occurred.
- **The exact error message:** Copy the full error text as it appears on screen (e.g., **request failed: 400**).
- **The hero image prompt you submitted:** Include the full text of the prompt that triggered the error.
- **Timestamp:** Note the date and approximate time when the error occurred.
- **Steps you already tried:** Any actions you took before or after the error appeared, including which self-serve steps above you attempted.

## **✅ Next Steps**

Having the information above ready will allow our team to identify the cause and apply the correct fix without unnecessary back-and-forth.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.