- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
06-28-2022 10:50 PM - edited 06-28-2022 10:51 PM
When the integration is used on non-existent hash:
!file file=2795b688bb5918e092e0ee33cd25aa98
Then it end with error:
Reason
MD5 | 2795b688bb5918e092e0ee33cd25aa98 |
Result | Not found |
06-29-2022 05:34 PM
Hi @Blazej_Gomoluch, Seeing that the response is 404, not sure if they will change it. If you're using this command inside a playbook, I have some a workaround for you.
You can ignore error and continue.
If not using 6.8, you should see a toggle at the bottom of the task window called "Stop on Error". You can then check for an error like below.
07-18-2022 03:19 AM
The !file command is using all the integrations at once. So doing it like this is not really a solution for me. I would like to bail on error if such occurs. But if there are no results I would like that all the integrations behave the same way (no error on 404).
I think I will modify the integration in my environment myself for now.
07-18-2022 06:47 PM
Hi @Blazej_Gomoluch, You can call the !File command against a single instance or integration with the "using" parameter. In the playbook task its located in the "Advanced" tab.
You can also handle the error via an automation using the above "using" parameter. Modifying an integration should be a last resort since you will no longer receive updates.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!