Known Issues

issue 1 elastic keyword search limited to 10,000 results affects bulk edit description when elasticfulltextsearch is enabled, keyword search results are limited to 10,000 records if more than 10,000 matching records exist, only the first 10,000 are returned attempting to navigate to the last page of results may also trigger a 500 error because of this limitation, when performing bulk edit/delete on more than 10,000 records, the confirmation dialog may display an incorrect count the operation is still applied to all matching records, not just the first 10,000 issue 2 field value text not displayed in search results when using elastic keyword search with nan/infinity values description with record full text search now running on the new, improved search engine, there is a discrepancy in handling special numeric values such as nan and infinity these values are currently indexed as null full text and keyword searches using nan or infinity will not return records containing these values in search results, numeric record fields that originally contained nan or infinity will be displayed as null issue 3 error when adding classic playbooks during new correlation settings creation description if a classic playbook is selected in the correlation settings while creating a new configuration and the user attempts to save, the system returns the error\ invalid data sent to server this issue does not occur in the following scenarios editing an existing correlation settings configuration and then adding a classic playbook adding a classic playbook to correlation settings after the configuration has already been created issue 4 playbook export fails when linked application is deleted description when an application is linked to a playbook through a correlation field and the application is subsequently deleted, attempting to export the playbook results in a failure the export process cannot complete successfully because of an orchestration task reference that remains in the playbook issue 5 filters updated in yaml for “record create” trigger not reflected in ui description filters updated in the yaml file for the “record create” trigger are not reflected in the ui however, changes made in the ui are properly saved and updated in the yaml this creates a one way sync from ui → yaml, but not from yaml → ui issue 6 filters in “record create” trigger not visible in ui if sub playbooks are missing from ssp package description when a playbook is exported without its sub playbooks and then imported as an ssp package, filters configured in the “record create” trigger are not visible in the ui, even though they still exist in the yaml file this creates inconsistency between the backend configuration and what is displayed in the ui issue 7 duplicate email sent after 1 hour custom notification description when the “get email notification” setting is configured for 1 hour, users correctly receive an email summarizing actions within the expected window (about 55–65 minutes) however, immediately after this notification, a duplicate email is sent in the same thread containing the same set of actions this results in duplicate notifications for the same activity issue 8 preset date range values use end expressions description the preset date range options this week, this month, this quarter, and this year are currently resolving to end expressions instead of the expected start based expressions for example this month resolves to endofmonth instead of now/m this quarter resolves to endofquarter instead of now/q this year resolves to endofyear instead of now/y this week resolves to endofweek instead of now/w this issue has been identified and will be corrected in the next release issue 9 highlighted date range disappears in dashboards after page refresh description when a start and end date are selected in the calendar, the range is correctly highlighted however, after refreshing the page, the highlighted date range is no longer visible, even though the start and end date values remain present in their respective fields issue 10 card displays timestamp instead of relative date range description when a relative date range is selected at the card level filter, the filter ui correctly shows the relative range however, the card itself displays a specific timestamp instead for example, if a user selects “last 1 hour” , the filter selection shows correctly, but the card displays a timestamp rather than the relative range while the dashboard view still shows the relative range, editing the card does not make it clear whether a relative range was originally selected issue 11 homepage not created for user in new tenant after changing tenant in role description when a role is moved from one tenant to another, the homepage for the assigned user is not created in the new tenant as a result, when the user logs in under the new tenant, no homepage is displayed issue 12 orchestrator user sees all reports in another user’s homepage description when an orchestrator user navigates to another user’s homepage through homepages > user’s home , they see all reports regardless of the permissions assigned to that user report visibility is not being filtered according to the target user’s permissions, allowing the orchestrator to view the full set of reports issue 13 playbook trigger by array value does not initiate run description when using an array field value as a playbook trigger condition, the trigger does not initiate the playbook run even when the condition appears to match, no run history is recorded issue 14 asset input missing for collaboration – google settings description in turbine 25 3 0, the asset input delegate account is missing from the collaboration – google settings asset because the parameter is not present in the schema, it does not appear in the ui workaround if you need to update or configure delegate account, manually add it to the asset schema once added, it will appear in the ui and can be updated existing configurations that already included the parameter continue to work and are not affected issue 15 component creation does not preserve loop references in native actions description when you create a component from a native action that is inside a loop, the loop reference is not replaced with a new component input as a result, the loop mapping is lost, and the component fails at runtime because it no longer receives the required loop value for example, if you create a component from a script or transformation action that is referencing a loop value, the new component is added to the canvas but no new input is generated to handle the loop reference this breaks the execution when the component is run issue 16 target string removed after changing the string operator description when you change a string operator in a playbook condition, the previously set target string (right operand) disappears after you click apply and reopen the configuration this results in the condition being incomplete and can cause unexpected behavior in playbook execution issue 17 filtering tenants by name or id in roles and configuration manager description when using the tenant filter in the roles page or configuration manager, the filter checks against both the tenant name and the tenant id because the dropdown only displays tenant names, filtering with numbers may show results that appear unrelated, since the number may match a tenant id behind the scenes for example searching 123 will return a tenant named 123 it may also return other tenants whose tenant ids contain 123 issue 18 playbook ids are displayed during export description when exporting playbooks, the ui incorrectly displays playbook ids alongside the playbook names issue 19 error when applying "select a date range" filter for the first time description when you apply the "select a date range" filter for the first time on a dashboard, the system throws the following error in the console this issue occurs only on the first use of the filter subsequent uses work as expected issue 20 reports with removed permissions still appear in recent dashboards for non admin users description when a non admin user initially has permission to access reports and later loses that permission, those reports may still appear in the recent dashboards list clicking such a report causes the page to remain in a loading state issue 21 non admin users cannot access applications they have been granted access to description non admin users who are granted read access to an application may still encounter issues accessing it when they log in and try to open the application, the system displays unauthorized errors the issue persists even when navigating back and attempting to re access the same application issue 22 unauthorized page persists after re login description when you log out of the application from an unauthorized page and log in again, you are redirected back to the same unauthorized page instead of the correct landing page if you switch accounts and then return to the original account, the unauthorized error is cleared, and you can navigate to all pages successfully issue 23 system error when no events are available in the last 24 hours description a system error can occur when a tenant does not have any events in the last 24 hours this issue only triggers in the absence of recent events and does not affect core functionality