Data could not be fetched in agent's FIM events
| Wazuh | Elastic | Rev | Security |
|---|---|---|---|
| 4.3 | 7.x | 4301-1 | Basic, ODFE, Xpack |
| Browser |
|---|
| Firefox |
Description When accessing an agent, if we click on the path of any FIM event, we cannot obtain information. In addition, the option to see the complete error does not work.
*Preconditions
- Demo environment
Steps to reproduce
- Navigate to Agents>Specific agent
- Click on FIM: Recent events>Path
- Click on See the full error
Expected Result
- Get more information
- If it fails, see the full error
Actual Result
- Data could not be fetched for
/tmp/agent.conf - See full error button does nothing
Screenshots
Uncaught TypeError: right-hand side of 'in' should be an object, got boolean
https://user-images.githubusercontent.com/80041853/165348662-505c5f07-47b6-4ad0-ba6f-4d8dc8311232.mp4
The API does not return data sometimes in the environment. The UI does not render the error adequately.

The failing paths do not appear to be included in the agent's inventory. We need to further investigate the error and check the database. It might be related with a problem in FIM core side.
The issue with the toast not showing an error string and the button of ¨Show the full error¨ not working might be related to https://github.com/wazuh/wazuh-kibana-app/issues/4030
We need to confirm is this error appears in previous versions.
Testing PR
- The solution only fixes the error when click on error toast to see more details ("
See full error") Could be tested usingSample Data FIM
testing on kibana 7.10 OK

I reopen this issue as the toast was fixed but some paths do not return any information when they should.
Hello, greetings to the community.
I would like to know if this point could be solved. I currently have wazuh version 4.7.5, app revision: 02 and I have this problem:
Data could not be fetched for c:\users\user\directory\file.txt (example)
Full error:
Error: File not found at FlyoutDetail._callee$ (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6181020) at tryCatch (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:786910) at Generator.invoke [as invoke] (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:790926) at Generator.next (https://xxxxx/47402/bundles/plugin/customImportMapDashboards/customImportMapDashboards.plugin.js:13:788105) at flyout asyncGeneratorStep (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6175519) at _next (https://xxxxx/47402/bundles/plugin/wazuh/wazuh.chunk.10.js:1:6175836)
Hello, I would like to know if the issue discussed was resolved??
NO still issue appears and many users face this issue, i think all