This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About amurret
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About amurret
01-25-2023
15Posts
1Like
1Solution
Jan 25, 2023Last Visited
User
Activity
User
Profile
Latest posts by amurret
| Subject | Views | Posted |
|---|---|---|
| 63 | 01-25-2023 06:59 AM | |
| 48 | 01-24-2023 12:31 PM | |
| 105 | 01-24-2023 12:28 PM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 01-24-2023 12:28 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 10 Likes | |||
| 4 Likes | |||
| 2 Likes | |||
| 2 Likes | |||
| 5 Likes |
User Badges
Community Statistics
| Member Since | 09-18-2017 08:40 AM |
| Date Last Visited | 01-25-2023 10:20 AM |
| Posts | 15 |
| Total Likes Received | 1 |
01-25-2023
06:59 AM
If the timeout is still showing the old timeout (not the one you configured in the Server config- you probably need to check this in a debug-mode log or set the instance to debug level logs and then view the integration-instance or server.log from the server to see what the actual timeout is for fetch-incidents) then it isn't using the new timeout you set. Do you have the integration name or the instance name in the server config? Note that it is the integration name, not instance name, and unless you have a custom integration with the above name in your screenshot you probably have the instance name in your current server config. Also, are you able to reduce max_fetch and/or first fetch time in the instance config?
... View more
01-24-2023
12:31 PM
It's possible you need to run /reset_containers for it to take effect?
... View more
01-24-2023
12:28 PM
1 Kudo
Hi Shreyash, if this is an automation, you can adjust the timeout in the automation settings. If it's an integration command, you should be able to set the below server config to increase the timeout for that particular command:
Key
Value
Default
< integration_name>. < command_name>.timeout
Timeout in minutes for specific integration command for brand names (leave the spaces in the name). The command name for fetching incidents would be fetch-incidents.
3
For reference, please see https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.8/Cortex-XSOAR-Administrator-Guide/Installation-Server-Configurations
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
01-25-2023
10:20 AM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks