Wsretry job is picking up tasks from other endpoints which are not included in Job configuration

[sk]

Team,

We noticed that in our environment wsretry task is picking the tasks from other security systems/endpoints which are not even selected in security system list of wsretry job.

We can confirm that we don't have any other instance of wsretry job running in our environment

Wondering how it is possible?

Job Configuration:

In above screenshots you don't see google endpoint/security system but you can see below tasks from google endpoint are completed successfully, Also we don't have instant provisioning enabled on respective endpoint

Completed Tasks:

Another question I want to clarify is, in case if we don't want to use any filter in job, Can we run wsretry task job without any filters(security systems, task types or advanced query) which should take care of tasks from all endpoints?

[pruthvi_t]

Hi @sk ,

Did you verify the update date of tasks completed and checked if they're picked in the same provisioning job that was ran as per the scheduled trigger?

For your question, if you're not mentioning any filters on trigger level and if you do not have any specific requirements, then your can remove the filter on applications and advance configs so that WSRETRY will pick all the pending tasks in the queue. However the processing times depend various things like number of pending tasks in the system at the time of job run, if multi threading is enabled or not etc.,

If my understanding of your question is not accurate, kindly let us know more on the ask.

Thanks

[sk]

@pruthvi_t : Thanks for confirming that we can run wsretry task without any filter. Coming to the issue, our job runs every 5 mins and the tasks that are completed will fall under the same time frame when job ran. 

[pruthvi_t]

@sk , if there is no other WSRETRY job running (standalone trigger/trigger chain) and instant provisioning is not enabled, there is no way the tasks should be picked if the application is not mentioned in the WSRETRY trigger. 

Kindly raise a FD ticket to have the situation looked into.

Thanks

[sk · Accepted solution]

We are able to identify the cause of this issue.

Root cause: We have filter applied at system as well as advanced configuration using sql query based on task types. Looks like with both system filter and advanced query is configured it is giving priority to advanced query and working based on that and ignoring system filter.