Skip to main content

8.3.0 Known Issues

· 5 min read

Updated 10/21/2025

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.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 is now able to see EAM Agents before and after they have been approved on the master Controller.

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​

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.

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.

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.

Security & Identity​

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.