Error messages¶
The most common messages Bramble shows while you set up, run and review simulations, and what to do about each. For messages from failed pre-checks and solution checks, see the checks reference.
Messages appear in these places:
- The Summary tab of a Run: stage icons, messages at the top of an Attitude's column, and tooltips on disabled buttons.
- The Run Checks tab, for failed checks.
- Pop-up messages at the top right, when a request fails.
- Lifecycle emails, if you've turned on Receive Lifecycle Emails in the Run page's cog menu. The subject says which stage failed.
A failed stage doesn't show its cause in the app. Open the Run's Logs tab. See handle a failed Attitude.
Summary tab¶
| Message | Where | What to do |
|---|---|---|
| "Failed" | Stage icon | Open Logs, or Run Checks for Pre-Checks and Check the CFD solution. Fix the cause, then Reset or Skip Failed Task. See handle a failed Attitude |
| "Insufficient Credits" | Stage icon, and the Insufficient Credits | Reset button | The Account can't pay for the simulation, or isn't active. Add credit or contact support@bramblecfd.com, then click Insufficient Credits | Reset and launch again. See credits and billing |
| "Waiting for Baseline to complete Mesh & Solve" | Create Delta PostPro icon | Not an error. Delta postpro runs automatically when the baseline has solved. See set a baseline |
| "Unknown Status" | Stage icon (bug icon) | Contact support@bramblecfd.com |
| "Attitude not in baseline" | Top of the column (warning) | The baseline Run has no Attitude with the same name, so this Attitude gets no deltas. Fine if the Attitude is new |
| "No parts in model" / "Run has no Parts." | Top of the column / Launch tooltip | Add Assemblies to the Run |
| "Following Vehicle has different Methodology" | Top of the column | Following-vehicle cases must use the same methodology as the lead. Fix the CFD setup |
| "Create Failed: …" | Top of the column (Star-CCM+ only) | The Create stage failed with the message shown. Fix the Template Case or geometry, then Reset |
| "Mapped Solution Donor Case has not completed solve stage." / "Waiting for donor case to complete Mesh and Solve stage." | Top of the column / Mesh & Solve tooltip | The donor Attitude hasn't solved yet. Wait for it, or solve it first |
| "Mapped Solution Donor Case has been archived." / "Donor Case has been archived." | Top of the column / tooltip | Archived Attitudes can't be donors. Choose another donor in the CFD setup |
| "Transitions disabled for this attitude." | Button tooltip | A request is in progress. Refresh the page |
| "Cannot reset an example Run." / "Cannot reset a Symlinked Run." | Reset tooltip | This Run can't be reset. Create a child Run and work on that instead |
| "Skipping a failed Mesh and Solve stage will likely result in the failure of remaining lifecycle actions." | Skip Failed Solve dialog | Check the logs first. Usually Reset is the better choice |
| "This is disabled in example projects" | Re-run tooltip | Re-run isn't available in example Projects |
Runs page and Run setup¶
| Message | Where | What to do |
|---|---|---|
| "This Run has no parts attached" | Group Launch | Add Assemblies to the Run |
| "Could not create run" / "Could not create child run" | Pop-up | Check the Kinematic Setup is complete ("Could not create run: kinematic setup is not complete") and that the Map and Kinematic Setup belong to the Programme |
| "Cannot create child with archived run" / "Cannot create child because some attitudes are archived" | Create Child Run tooltip | Use a Run with no archived Attitudes as the parent |
| "Child cases can not be created from an optimisation run." | Create Child Run tooltip | Choose a different parent Run |
| "Please create a Template Case for the current Programme first" | Project baseline and Create Child tooltip | Create a Template Case in the Programme |
| "One or more attitudes are not completed" | Archive tooltip | Sign off every Attitude in the Run first |
| "The selected Workflow and Queue are Incompatible." | CFD Attitude Setup | AWS workflows need AWS queues, and the other way round. Choose a matching queue or workflow |
| "Could not update CFD Setup" | Pop-up | The CFD or PostPro setup wasn't saved. Check the Attitude can still be edited (not launched or archived), then try again |
| "Could not set mapped inlet source" / "Could not set mapped solution donor." | Pop-up | Try again. If it keeps happening, contact support@bramblecfd.com |
| "Could not reset case", "Could not abort case", "Could not skip case", "Could not rerun postpro case" | Pop-up | The lifecycle request was refused. Refresh the page and try again |
PostPro¶
| Message | Where | What to do |
|---|---|---|
| "Postpro Setup cannot be changed on Demo Runs" | PostPro Setup save tooltip | Example Runs can't be changed |
| "Cannot generate camera sets on a run with no assemblies" | Generate Camera Set tooltip | Add Assemblies to the Run |
| "Could not update extra deltas" | Pop-up | The extra deltas weren't saved. Try again |
| "Error Saving Postpro Settings" / "Error Loading Postpro Settings" | Postpro Settings page | Check every mandatory field is filled in, then save again |
| "should contain at least one default value" | Postpro Settings page | Keep at least one default row on each tab |
See configure postpro.
Logs and Results¶
| Message | Where | What to do |
|---|---|---|
| "No logs available" / "Error loading log" | Logs tab | There are no log files yet, or they've been deleted by Reset or archiving. Otherwise click the refresh icon |
| "Invalid Delta Baseline" / "This case has no linked map" | Results pop-up | A Map Relative delta baseline needs an Attitude from a Run with a Map. Choose another Attitude, or a different delta mode |
Check failures¶
Failed checks are listed on the Run Checks tab, and in lifecycle emails for a failed Pre-Checks stage. For what each check tests and what to do, see the checks reference.
Related: Handle a failed Attitude · Statuses and lifecycle · Checks · CFD setup options