Skip to main content

8.3.0 Known Issues

· 4 min read
Susan Shamgar
Technical Writing Supervisor

Updated 01/20/2026

The following issues were detected prior to the release of Ignition 8.3.0 as items that would not work as expected at the time of launch. This page will continue to be updated as these issues are addressed in future versions. Note that this is not an exhaustive list of all bugs.

The primary support channel for any questions or feedback is the 8.3 Early Access forum.

Fixed in 8.3.3​

EAM & Redundancy​

  • Disabling the Gateway Network on a redundant master disables the same setting on the backup. The Enabled setting must be re-checked on both Gateways to successfully restore the connection. To allow this, the General Gateway Network settings can now be modified on a backup Gateway. Any other General Gateway Network settings changed on the backup will be overwritten with the master settings once the nodes are synced.

OPC UA​

  • The OPC Quick Client is now available again, allowing users to browse and test OPC UA items directly from the Gateway.

SECS/GEM​

  • SECS/GEM pages are now available on the Gateway when the SECS/GEM module is installed.

Security & Identity​

  • The unsupported Retention setting has been removed from the Gateway UI for Remote Audit Profiles.

Fixed in 8.3.2​

Historian & Store and Forward​

  • When upgrading an existing 8.1 Gateway, Audit Profiles will maintain the uppercase format and work as intended. New 8.3 installs may still see errors due to the difference in capitalization when connecting to an 8.1 database where an Audit Profile exists.

Tags & UDTs​

  • Tags with custom properties using the name valuePersistence or defaultValue will now log their property values to the migration log and will no longer be overwritten upon upgrade.
  • The Remote Tag Provider will no longer display warning or error messages when deleting shelved alarms or when attempting to unshelve the alarms for deleted tags.

Security & Identity​

  • Users no longer need to clear session cookies to log into the Gateway after setting up HTTPS and deleting the web server TLS certificate.

Fixed in 8.3.1​

EAM & Redundancy​

  • Scheduled tasks will now execute after a failover.
  • When users have a controller set up within a redundant pair, the backup controller Gateway is now able to see EAM Agents before and after they have been approved on the master controller Gateway.
  • Users can no longer create or select invalid controllers within the EAM Setup Wizard when setting up an EAM environment.

Event Streams​

  • Event Stream startup and shutdown actions are now handled by separate threads so that they can run independently of each other to ensure the lifecycle of one event stream doesn't affect the lifecycle of another.

Historian & Store and Forward​

  • When upgrading to 8.3, Historian modules and related JDBC drivers are no longer installed if they were not present in 8.1.

Alarming​

  • Active alarms will now display correctly in the Alarm Status Table component.
  • Edge alarm events will now sync as expected on remote Alarm Journals on a standard Gateway.

Designer & Scripting​

  • The Designer will no longer have errors finding updated projects when the Gateway redundancy role is set to Master.
  • Scripting requests using system.util.sendRequestAsync will now function as expected.
  • The Merge to Logs action on the Gateway Scripts webpage will now correctly apply filters.

Security & Identity​

  • Internal Identity Providers with spaces in their names are now accepted.
  • The system.user.editUser function will now work as intended when editing users in a AD Internal Hybrid User Source.

Known Issues​

EAM & Redundancy​

No log messages appear when an EAM Edge Agent paired with a standard Gateway does not receive resources​

If a user sends resources to a target project that doesn't exist on the Edge Gateway, it can't make a project to catch those resources like a standard Gateway can. While this is the intended behavior, there is no logging to indicate that anything happened.

Reporting​

Master Pages​

This feature was initially targeted for 8.3.0, but was trimmed from scope. This will be added in a future release.

Historian & Store and Forward​

Renaming a database prevents Store and Forward engine from forwarding data​

If you rename a database connection, the Store and Forward engine does not update its configuration. Forwarding stops, and only a WARN log message is generated.

Web UI​

Update response toasts are not properly displaying 422 messages​

If users see a JSON object inside of an error dialog, it's likely due to this known issue.

Mobile-Responsive Gateway UX​

Changes to the Gateway UX to improve mobile responsiveness are planned for an upcoming release.

401 error on Gateway homepage when not logged in​

The homepage may continuously log 401 errors in the console when accessed without authentication.

Maker edition incorrectly allows redundancy setup​

The Maker edition Gateway allows users to configure redundancy in the UI even though it is not supported.

Ignition 8.3 Release Timeline

· One min read
Nichole Boehnke
Docs Team

Updated 8/13/2025

Ignition 8.3 is the next major version of the Ignition software. Many new features were highlighted and demonstrated at ICC 2024, such as the redesigned Gateway UI, Perspective module upgrades, and new Historian features.

Target Final Release Date: 9/16/2025

This document will continue to be updated with release announcements and specific dates as they are finalized. Additionally, keep an eye out for a What’s New in 8.3 overview and 8.3 Upgrade Guide for more information on what to expect.