and more in a single search tool across platforms. Read the announcement here. |
03/23/2024 02:47 AM
Hi,
We are trying to launch entitlement owner campaign. And it is getting stuck in launching mode. With same template it was working fine in 5.5. Is this an issue?
Regards,
Indranil Biswas
03/23/2024 12:18 PM
@indrahema95
Can you specify which version you are observing this behavior?
03/23/2024 12:26 PM
@stalluri 23.12
03/23/2024 01:30 PM
Update the ES timeout configuration to minimum value of 300,000. If the value is already set as 300,000 then the value can be increased in increments of 300,000 to max value of 2400,000.
To update the settings go to Admin -> Global Configuration -> Search for 'Time out'. Please update all 3 timeout configurations shown below:
03/25/2024 12:18 AM
03/24/2024 06:56 PM
If you use query based on account_entitlements1 which taking long time then this issue occurs . Optimize your query.
03/25/2024 12:17 AM
03/25/2024 08:10 PM
> 0 is causing issue , Can you provide your requirement to provide better query
03/26/2024 06:37 AM - edited 03/26/2024 06:38 AM
Hi @rushikeshvartak We want the entitlements which has at least one or more accounts associated it.
Regards,
Indranil
03/26/2024 08:24 PM - edited 03/26/2024 08:25 PM
Use below conditions
03/24/2024 11:03 PM
@indrahema95 I had a similar case , and followed following process :
1. Initially we opened an FD and found the issue was with Elastic search. The crawler was stuck and due to which even a simple campaign/analytics was not running. The Ops team helped us to fix the issue.
2. Later, when we tried to setup our actual use case (tiered campaign) we found out the query which we added in Account Entitlements1 Query caused an issue.
Make sure you validate both.
03/25/2024 12:16 AM
Hi @Manu269 , we are using the below advance configuration.
The strange thing is that, sometimes it works and sometime is not working(mostly).
We are also facing issues in analytics also. Is this because of problem in elastic search?
Regards,
Indranil Biswas
03/25/2024 09:12 PM
For me it was with elastic search.
Ended up with opening the ticket with Saviynt Ops.
You should see an error in logs regarding the es search.