Updated 10/07/2025
The following issues were detected prior to the release of Ignition 8.3 as items that would not work as expected for the official release. This page will continue to be updated as issues are addressed. Note that this is not an exhaustive list of known issues.
The primary support channel for any beta questions or feedback is the 8.3 Early Access forum.
EAM & Redundancy
Disabling Gateway Network on Master also disables it on Backup
Disabling the Gateway Network on a Redundant Master also disables it on the Backup. This behavior is different than in 8.1. This will be corrected in a future release.
Back up controller unable to see EAM agents
When users have a controller set up within a redundant pair, the backup controller is unable to see EAM agents before and after they have been approved on the master controller.
Users are able to create/select invalid controllers when setting up an agent
When setting up an EAM environment, users are able to create/select invalid controllers within the agent setup wizard.
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.
EAM Scheduled Tasks fail to resume after redundant failover
Scheduled tasks may stop executing after a failover and remain suspended on both Gateways.
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.
SECS/GEM
SECS/GEM Gateway pages are not present
SECS/GEM pages are not currently visible on the Gateway. These 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.
Upgrading from 8.1 installs Historian modules even if not previously installed
When upgrading to 8.3, Historian modules and related JDBC drivers are installed even if they were not present in 8.1.
PostgreSQL audit profile error
Audit Profiles using PostgreSQL may display errors that certain columns (such as event_timestamp) do not exist, even though the schema is correct.
Tags & UDTs
Some custom tag properties overwritten upon upgrade
If a user has created a Tag Custom Property name of valuePersistence or defaultValue, there will be issues with those properties, as there are now standard Tag properties with those names. In 8.3.0, these properties will be treated as standard properties, and the values that were assigned to those properties in 8.1.* will be overwritten with the default value of those properties in 8.3.0.
Remote Tag Provider becomes unresponsive after attempting to unshelve non-existent alarm
The Remote Tag Provider can become unresponsive if a user attempts to unshelve an alarm after the tag for that alarm is deleted.
Alarming
Alarms not showing active in Alarm Status Table
Some active alarms may not display correctly in the Alarm Status Table, even though they are present in the system.
Edge alarm events not syncing to remote journal
Edge alarm events may fail to sync to a remote Alarm Journal on a standard Gateway.
Designer & Scripting
Designer error when redundancy role is Master
In some cases, the Designer may show “Error reading updated project from Gateway” or “Project 'null' could not be found” when the Gateway redundancy role is set to Master.
Idle socket detection timeout can end scripted requests early
Long-running scripted requests using system.util.sendRequestAsync can be terminated before their defined timeout due to idle socket detection.
Gateway Scripts "Merge to Logs" does not apply current filter
When using the Gateway Scripts page, the Merge to Logs action does not apply the current filter to the main Logs page.
Security & Identity
Internal Identity Providers with spaces in their names fault
If an internal Identity Provider contains a space in its name, it will fault and login attempts fail.
AD/Internal Hybrid system.user.editUser regression
Editing a user in a hybrid AD/Internal source may fail when a user exists on both sides with the same name.
Session cookies cause 401 errors after HTTPS changes
After configuring HTTPS and making certificate changes, sessions may fail with 401 errors when switching between HTTPS and HTTP.
Remote Audit Profiles incorrectly display Retention option
The Retention setting is shown in the UI for Remote Audit Profiles even though it is not supported or functional.
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.
OPC Quick Client
The OPC Quick Client is not included in the 8.3 beta release, but will be added in a future release.
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.