The following items are notable issues fixed between the release of SystemLink 2021 R2 and SystemLink 2021 R3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of SystemLink.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1531598 |
Systems Browser - Build Query slide out becomes unresponsive after removing blank query itemWhen using the Build Query slide out to create a filter from the Systems Browser, it is possible to get into a partially unresponsive state. One way to get into this state is via the following actions:
To confirm this is the behavior you're seeing, open your browser's development tools and navigate to the console tab. Repeat the steps that caused the failure and you should see the following output:
Workaround: option 1: Press the blue "+" button again to add a new item. All items in the query should become responsive again. Delete any unused query items once you've configured the query fully. option 2: Press the "Cancel" button on the slide out and recreate the desired filter, avoiding the steps that caused the failure.
|
Reported Version: SystemLink 2021 R2 Resolved Version: SystemLink 2021 R3 Added: Jul 19, 2021 |
|
1706828 |
DataFinder stopped because SL TDM Database Service crashedWorkaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.1 Added: Nov 24, 2021 |
|
1703771 |
Analysis Automation quick action "Go to task definition" does not workWorkaround: Click Refresh in your browser and then use "Tasks" tab to navigate to task definition.
|
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.1 Added: Nov 24, 2021 |
|
1939802 |
Steps may incorrectly be marked as failed or timed out when using Store and ForwardStored requests that do not have a unique timestamp can be incorrectly sorted and forwarded out of order. Depending on the order, different symptoms can occur:
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R1 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1958992 |
Store and Forward Service may crash when there are too many items in quarantineBatch forwarding, a new feature added in the 21.5.1 SystemLink Client reads the entire store directory into memory before forwarding. When the store directory is too large, this results in significant memory consumption, which can crash the service or result in undesirable side effects. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1939771, 1944740 |
Reports may not be attached to Test Results when using Store and Forward in the TestStand TestMonitorClientXML, PDF, System Software, and Asset Reports may not be properly attached to the test result when store and forward is being used. This is caused by a race condition that may mark the result update as complete before the reports have been attached, or if the System does not currently have a connection to the SystemLink Server. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1955444 |
Store and Forward files may not be removed from disk after forwarding is completeIf multiple store and forward files have CloseFile updates with the same timestamp, only one will be removed from disk. This may result in extra files remaining on disk unnecessarily.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1953405 |
Steps and Results created by TestStand when Store and Forward is enabled may have an incorrect 'Started At' timeSteps and Results that are created by TestStand when Store and Forward is enabled will have a 'Started At' time that reflects when they are created on the server rather than when the test ran.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1939944 |
Unhandled Exception in the TestMonitor plugin may cause the Store and Forward service to crashIf an unhandled exception occurs in the TestMonitor plugin for TestStand when Store and Forward is enabled, the backing service may crash when forwarding quarantined Step or Result data. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1947039 |
Unstable network connection may cause Store and Forward to skip requestsIf forwarding is interrupted due to poor network connectivity, items with the same timestamp may be skipped when forwarding is resumed.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
|
1986882 |
Memory leak in Test Monitor ClientThe Test Monitor Client has a small memory leak, the severity of which varies based on the number of steps run and the amount of data stored.
Workaround: Restart TestStand to clear the leaked memory. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2 Added: Jun 10, 2022 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.