One of our certification campaigns has been stuck in a launching status for a while. Upon checking global configuration for Elasticsearch timeout, I see that it has been set to 30000 (30 thousand milliseconds) only (see screenshot below). I understand that the recommended minimum is 300,000 (milliseconds). But before making this adjustment I wanted to understand the overall impact of changing this configuration.
What are the functions in Saviynt that are affected by this change? Also, it takes quite a long time even for a small certificate campaign to move from launching to preview state. Will changing the timeout configs help resolve this issue as well? Any documentation or information would be helpful.
Hi @NPY ,
Modules that can be affected are Campaigns and Intelligence/Analytics.
Timeout configs will definitely help launch the campaign faster. Refer the post - https://forums.saviynt.com/t5/community-knowledge-base/campaign-stuck-in-launching-state/ta-p/20948