CodeRunner 8.17.7
New features
Remove Gemini username/password support
- The option to log in to Gemini with a username and password has been removed, as it is no longer supported by Gemini.
- You no longer need to log in to Gemini and Gemini Exit separately, as the same credentials can be used for both.
- Various configuration screens have been simplified, as options related to Gemini passwords have been removed.
Allow entry capacity trades to be accepted in CodeRunner
If a counterparty has posted a Gemini capacity sale to you, you can now accept this from the Trading and Long Term Booking screen in CodeRunner.
Allow configuration of Gemini Operator EIC code
The EIC code of the Gemini Operator can now be configured in the CodeRunner Gemini config file. This is used when making IP nominations and retrieving IP confirmations.
CodeRunner 8.16.1
Re-added the ability to configure separate Gemini and Gemini Exit OAuth 2 credentials, following changes to the Gemini release schedule by National Gas.
CodeRunner 8.15.12
Change OAuth 2 API paths
We have updated the paths used when connecting to Gemini using OAuth 2 over the internet. This means that CodeRunner cannot connect to the current Gemini system using OAuth 2, but will be able to connect to the new Gemini system when the upcoming Gemini changes go live. You can still also connect to the current Gemini system with a username and password until Gemini stops supporting this.
CodeRunner 8.15.10
New features
Configure new Gemini OAuth 2 credentials
It is now possible to configure OAuth 2 credentials in CodeRunner for connecting to Gemini. These can be used to connect to the Gemini and Gemini Exit APIs over the internet, and will soon be the only way for applications to connect to Gemini. OAuth 2 credentials are configured in a new screen and access to this screen can be restricted to specific user groups if required.
Log in with OAuth 2 credentials
When OAuth 2 credentials are saved, you must set a security key which is required by any users who want to log into Gemini. This security key should be stored and shared securely with team members (e.g. using a password manager). When you log into Gemini using CodeRunner, you can enter the security key to connect using the new method.
Note that you can also continue to use your existing usernames and passwords, until National Gas remove support for them later this year.
Other changes and improvements
- The location for new capacity bids on the Daily Bids and Scaleback screen is no longer pre-populated, to minimise the risk that a bid is accidentally placed for the wrong sub-terminal.
- Reports scheduled between 05:00 and 06:00 now use 05:00 as the start of the gas day to determine which gas date to run for.
- The email addresses shown in contingency forms have been updated to use nationalgas.com instead of nationalgrid.com.
CodeRunner 8.14.2
This release contains an update to the Moffat single-sided nominations functionality, so that double-sided Moffat entry nominations can be sent even if single-sided exit nominations are configured for the same shipper.
CodeRunner 8.14.1
New features
Support single-sided IP nominations for Moffat
It is now possible to configure CodeRunner to send single-sided nominations against adjacent shippers at Moffat, and poll for confirmations for these nominations. This can be set on the Adjacent TSOs or Counterparties maintenance screen.
Fixes and improvements
- Upgraded Oracle.ManagedDataAccess (a third-party dependency) to address a potential security vulnerability (CVE-2023-21893).
- Fixed a bug which caused reports scheduled to run every week to run a day early.
CodeRunner 8.13.5
New features
Add Gemini Quantities report
Added a new custom report which allows the export of Gemini forecast, nominated and scheduled amounts for multiple days in CSV format.
Automatically replace Gemini estimated amounts
Improved how the Nominations screen works with estimated amounts:
- An activity is no longer highlighted if there is an estimated amount of zero.
- The “Nominate?” check box is now automatically ticked for activities where there is a non-zero estimated amount.
Improvements to the installation process
Oracle.ManagedDataAccess.Client is now bundled with CodeRunner, meaning that the Oracle Client is no longer a prerequisite for customers using an Oracle database.
Previously any changes to the CodeRunner.exe.config file would be overwritten by the installer. The installer now instead creates a sample config file, which can be used as a reference, and the config file itself is not overwritten.
Fixes
Importing swing noms at 05:00 on 6-6 contracts deletes nominations for the following gas day
Fixed a bug where swing nomination imports via the XML interface could remove nominations for the following day if the contract was configured as 6-6 and the nomination started at 05:00.
CodeRunner 8.12.4
New features
Add Import Log screen and alerts for XML interfaces
A new Import Log screen has been added, which lets users see details of imports via the XML interface, and an alert which warns users of any import errors.
Use external codes in XML interface
External codes for locations and counterparties are now used when importing data via the XML interface. The ability to configure external codes for swing contracts has also been added.
Improve resilience of XML interface
If database connection is lost, files will be reprocessed automatically when the connection is re-established.
Standardise interfaces
The Weekly Policy Load and Actuals Import options have been removed, as all functionality is available through the XML interface and affected customers have been migrated.
Improve security of stored passwords
Implemented the PBKDF2 algorithm for salting and hashing user passwords, to enhance security for customers who do not use Windows authentication.
Update version of .NET Framework used by CodeRunner
Updated CodeRunner to require .NET Framework 4.7.2. This is a change to the prerequisites, but .NET Framework 4.7.2 should have already been automatically installed by Windows if you are on a supported Windows version.
Change to service installation
Changed the way sample config files for CodeRunner services are provided, to simplify the process of upgrading the services.
CodeRunner 8.11.1
Fixes
CVA export XML does not contain actuals with zero nomination when “Actuals at Master contract level” set
Fixed an issue with CVA exports that occurred if a contract has multiple sub-contracts, actuals are entered against the master contract rather than the sub-contract, the nominations at a flange are zero, and the actuals are non-zero.
CodeRunner: 8.11.0
New Features
Support for Weekly System Entry Capacity (WSEC)
The Capacity Trading and Long Term Booking screen now supports Weekly System Entry Capacity (WSEC). Capacity bids with Bid Type WSEC can be entered and Gemini Refresh will update CodeRunner with capacity bids of this type from Gemini. These bids are included in capacity calculations.
CodeRunner 8.10.10
New Features
Post, Modify and Withdraw capacity bids
The Daily Bids and Scaleback screen now supports posting exit and entry capacity bids to Gemini. Capacity bids can also be modified or withdrawn using the new 'Modify Selected' and 'Withdraw Selected' buttons. Any capacity bids posted from CodeRunner will be Evergreen.
Gemini Refresh button replaces Gemini Query and Update CodeRunner buttons
On the Daily Bids and Scaleback screen the 'Gemini Query' and 'Update CodeRunner' buttons have been removed and replaced with a 'Gemini Refresh' button. Gemini Refresh will update CodeRunner from Gemini.
Auto population of reserve prices for capacity bids
When adding a new capacity bid on the Daily Bids and Scaleback screen the reserve price can be populated in the price column. Reserve prices can be configured for each sub-terminal and bid type in the GeminiConfig.config file.
CodeRunner 8.9.0
New Features
Show size of capacity breaches
Previously, rows with capacity breaches in a number of screens were highlighted, but the 'Remaining Capacity' columns showed '0' so the size of the breach was not explicitly shown. The following columns have been changed to show capacity breaches as negative amounts:
- Remaining Capacity and Remaining % on the Entry Capacity, Exit Capacity and Swing Exit tabs of the Sense Check screen.
- Remaining Capacity on the Beach Positions screen.
- Surplus/Deficit on the Retro Trading Availability screen.
- Capacity Available (kWh) column on the Capacity Position tab of the Contingency and Extended Contingency Excel reports (note these are specific to a single customer).
A Remaining Capacity column has also been added to the Capacity Usage screen.

