Report an issue
Learn what to do when Atoms detects a build issue, how to use Resolve safely, and what information to send if the problem continues.
Learn what to do when Atoms detects a build issue, how to use Resolve safely, and what information to send if the problem continues.
Understand the Issue Report
When Atoms detects a build problem, the Issue Report notification appears in the bottom-left corner. Select Resolve to ask Atoms to attempt a fix, or expand the notification to view the Issue Report details on the right. The details may include the error message, command output, or other diagnostic information, depending on the error; copy only what the panel shows.

Issue Report and Resolve in the project Chat.
Try Resolve first
If Resolve is available, start one attempt and wait for it to finish before taking another action.
- Select Resolve and wait for the current attempt to finish. A typical attempt takes 1 to 3 minutes.
- Do not select Resolve again while it is running, because duplicate clicks can create duplicate tasks.
- When the attempt finishes, check the refreshed preview. If the preview does not update, refresh the browser once.
- Repeat the exact steps that caused the problem. If it remains, expand the Issue Report, review the Issue Report details, and continue to the reporting steps below.
If no Issue Report appears but the app behaves differently from what you expected, ask the Agent to investigate. Describe the action that triggers the problem, what you expected, and what happened instead. If the problem continues, report it using the steps below.
Report the issue
Use the following path when Resolve is unavailable, the problem remains after a completed attempt, the preview is unresponsive but the project Chat still works, or unexpected behavior continues after you ask the Agent to investigate.
If you are on the Free plan, use the official Atoms Discord community for peer help instead of the in-app Support route: Join the Atoms Discord. Atoms Support is available to paid users.
Open Feedback from an Agent message
- Open the affected project Chat and find the latest relevant Agent message that shows the ... (more options) control.
- Select ..., then select Feedback.

Open the Agent message’s more options menu.
Selecting Feedback opens Atoms Support. It does not send a report automatically; continue below and send a message to contact Support.
Send your report in the support messenger
- When the messenger opens, select Send us a message to start a new report.
- If the messenger says you are not logged in, select Sign in now, sign in to your Atoms account, then reopen Help or Support and continue.
- If you already reported the same issue, open Messages and select the existing conversation instead of starting another one.
- Follow the prompts, paste the report template below, attach the relevant evidence, and send the message.

Open the support messenger to send your report.
If you cannot use the project page
If the entire project page is unresponsive or no relevant Agent message is available, open the Atoms Help Center in another tab. On larger screens, select Support; on smaller screens, open More options and select Support. You can also use the bottom-right support-chat button. Select Send us a message, sign in if prompted, and include the affected Chat Link if you can access it.
What to include in your report
A useful report gives Atoms Support enough information to reproduce and recognize the same problem.
- Issue summary. Describe the problem in one or two sentences.
- Affected Chat Link. Include the URL of the Atoms Chat where the problem occurred.
- Date and time. State when the issue occurred and include your time zone.
- Steps to reproduce. List the exact actions in order, beginning from the state before the problem appeared.
- Expected result. State what should have happened.
- Actual result. State what happened instead and include the exact error message, if one appeared.
- What you already tried. State whether Issue Report and Resolve appeared, what happened after the Resolve attempt, and whether refreshing the browser changed the result.
- Browser and device. Include your browser, operating system, and device type.
- Screenshot or recording. Show the error and enough of the surrounding interface to identify where it occurred. If Drop files or images here appears, drag the file into that area.
- Relevant Issue Report details. Copy only the error or command details that the Issue Report panel visibly shows. If the text cannot be copied, include a screenshot of the visible details.
Issue summary:
Affected Chat Link:
Date and time, including time zone:
Steps to reproduce:
1.
2.
3.
Expected result:
Actual result:
Did Issue Report and Resolve appear?
What I already tried:
Browser, operating system, and device:
Screenshot or recording attached: Yes/No
Relevant Issue Report details or logs:Before sharing: If you are a paid user, send this information only through an official Atoms Support route. If you are on the Free plan, use the official Atoms Discord community for peer help instead: Join the Atoms Discord. Community help is not a guaranteed response from Atoms Support. Remove passwords, API keys, authentication tokens, payment details, and unrelated personal or confidential data from screenshots and logs. Keep only the sanitized error details needed to investigate the issue.
After you report the issue
Sending a report does not automatically change or fix your project. Keep the affected project and support conversation available. Replies from Atoms Support appear under Messages. If Support asks for more information, reply in the same conversation.
For other ways to get help, see Community & Support.
FAQ
How do I report a bug or request support?
Use the official in-app Support channel or the current Support address listed by Atoms. Include:
- Account email, workspace, and Chat Link or project URL
- Exact error text or code and a full screenshot
- Time and timezone
- Steps to reproduce
- Expected result and actual result
- Affected environment, browser, operating system, model, and project version when relevant
- Last time or version that worked
Before sending screenshots, logs, HAR files, or command output, remove passwords, tokens, cookies, personal data, payment details, and confidential project content. For a billing issue, include the Order ID but never a full card or bank-account number.