Nextmv Docs

The Nextmv platform accelerates teams with DecisionOps tooling, optimization integrations, and decision app quickstarts.

Recent releases

nextroute

v1.12.0

September 19, 2025

What's Changed

Full Changelog: v1.11.4...v1.12.0

Console

Download scenario test runs

September 19, 2025

A new feature was added to scenario tests that allows you to download all of the outputs of the runs made for the scenario test. You could always go to each individual run and download the output file, but this could be tedious if your scenario test had a lot of runs. Now with the click of a button all the run outputs are collected into a single ZIP file and downloaded to your local machine.

Downloaded run outputs will be grouped into directories based on the individual scenarios within the scenario test. Note that only successful runs will be downloaded. If one or more run outputs could not be downloaded for whatever reason, a notice.txt file will be included in the ZIP file that lists the IDs of the run outputs that could not be downloaded.

Two screenshots of the UI to download the runs, the first is a dropdown menu from the download button with a label that reads Download runs with 100 as the number of runs in a parenthetical next to it. The second is the same screenshot of the one next to it (the UI to download the runs), but showing what the in-progress state looks like: the Download runs label has been replaced with a green loading bar.

Console

Delete instances, inputs, and input sets

September 18, 2025

You now have the ability to delete instances, inputs, and input sets in Nextmv Console. To delete an entity, navigate to the edit view and in the lower right of the page, in the footer, there will be a Delete button. Click this Delete button and then confirm the delete action in the next step.

Screenshot showing the initial Delete entity button in the page footer at the bottom, in red, on the right

After clicking this final delete button, the entity will be deleted and you will return to the list view. Note that an instance set as an app’s default instance cannot be deleted in Console. It must first be unset as the app’s default instance, and then it can be deleted.

Screenshot showing the confirmation step asking if you want to delete the entity with a final, red Delete button.

The delete operation is available to Operator, Developer, and Admin roles. Viewer roles cannot delete entities.

Console

Clone individual scenarios in a scenario test

September 15, 2025

A new Clone scenario button has been added to the create scenario test view that enables cloning individual scenarios within a scenario test. This new feature allows you to quickly create new scenarios within a scenario test that are based on a scenario you have already defined. A cloned scenario carries over the full definition of its source scenario and then can be further adjusted as needed.

Screenshot showing the clone scenario button next to the name of a scenario in a scenario test.

nextpipe

v0.3.5

August 27, 2025

What's Changed

Full Changelog: v0.3.4...v0.3.5

nextmv-py

nextmv-v0.29.4

August 26, 2025

What's Changed

Full Changelog: nextmv-v0.29.3...nextmv-v0.29.4

nextpipe

v0.3.4

August 4, 2025

What's Changed

Full Changelog: v0.3.3...v0.3.4

nextpipe

v0.3.3

August 4, 2025

What's Changed

Full Changelog: v0.3.2...v0.3.3

nextplot

v0.1.9

July 29, 2025

What's Changed

New Contributors

Full Changelog: v0.1.8...v0.1.9

sdk

v1.9.3

July 29, 2025

What's Changed

Full Changelog: v1.9.1...v1.9.3

go-highs

v1.6.2

July 28, 2025

What's Changed

Full Changelog: v1.6.1...v1.6.2

go-mip

v1.6.2

July 28, 2025

What's Changed

Full Changelog: v1.6.1...v1.6.2

nextmv-py

nextmv-v0.29.3

July 24, 2025

What's Changed

Full Changelog: nextmv-scikit-learn-v0.3.2-dev0...nextmv-v0.29.3

Console

Decision workflows in Nextmv Console

May 14, 2025

Decision workflows are now available in Nextmv Console. You can create a new workflow from the UI and then manage the workflow like you would an application. A workflow has all of the same views as an application, except that the workflow run details includes an extra Flow view that displays a directed acyclic graph (DAG) of the workflow run.

Screenshot of the DAG diagram showing a flow with four steps that have succeeded. Each step is represented with a box that includes the name of the step and a short description, and a green check icon since each step succeeded. Two of the steps happen in parallel, so these are shown in the same column. Arrows connect the steps to show the order of the steps in the flow.

Read more about decision workflows and how to use them in the dedicated Decision workflows section in Nextmv Docs.

Console

Remember last visited team

May 13, 2025

Prior to this update, when you logged in to Nextmv Console, after being authenticated, you would be directed to your root account. If you wanted to switch to another team you would need to select the team from the dropdown in the header. This pattern could be laborious if you were doing most of your work in a team other than your root account.

Now, Nextmv Console will remember your last-visited team and you will be automatically redirected to this team when you log in.

Console

Human-friendly metrics

May 6, 2025

Applications can write custom metrics to the run output file using the standard Statistics convention. These custom metrics live under the top-level statistics property of the run output and are extracted and displayed in the run details view in Nextmv Console.

These metrics were displayed in a technical manner using their full data path as the name of the metric. For example, if a custom metric tracking total waste was named total_waste and was a property of the custom object which in turn was a property of the result object, the name of this metric would be displayed as result.custom.total_waste.

These object data paths were obscuring the meaningful parts of the metric names, and the end user often only cares about the metric and its value, not where it’s stored in the output JSON file. For these reasons, the metrics are now displayed without the data paths and also are presented with a more human-friendly title casing.

Before

Table view of data showing the old way of rendering property names with their full object dot notation paths that reference their location in the JSON block. The example from the note above reads result.custom.total_waste.

After

Same table view as the image above, but now the property names have had the JSON location paths removed. The example from the note above now reads just Total Waste.

Console

Updated acceptance tests

April 24, 2025

When creating a new acceptance test you can now specify a tolerance level for the pass/fail rules. Prior to this, you were only able to set hard rules on how a test would pass or fail. When setting the tolerance, you can define it as an absolute value (specific number) or as a relative value (percentage-based).

Screenshot of the UI in the create new acceptance test view that allows you to type in the metric you want to track and then define the tolerance type (absolute or relative) and the corresponding value.

This tolerance will be reflected in the final chart visuals as well.

Screenshot of a point and line chart that plots a target line running diagonally in the middle from lower left to upper right with a band of green on either side that visualizes the threshold for acceptable values within range of the target line. Points that correspond to the runs are plotted on top of this band to show which runs fall inside and outside of the threshold.

Release notes archive

How to get help

Contact us for Nextmv platform support.