@devops.kyc,

Apologies for the inconvenience caused.

There has been a massive build-up in the screening queue, due to which the screening requests are getting delayed. The async screening queue cannot be flushed as it may cause non screening of requests which would be flushed in the course, hence the team is monitoring and counting on the queue to clear itself and this may take some time. The delay in processing the screening request is expected till the pileup is cleared.

Considering the situation, we would advise you to use the sync screening approach instead of async screening.

Hope this helps.

Thank you for the status update.

1. Could you give an indication of how long this will take until async screening is operational again or is there any queue status publicly available so we can check ourselves?

2. Is it advised to always use sync screening instead of async screening, also on production environment? Or only now because of this issue in pilot?
Which one is recommended?

Thanks

@DSP,

1. The async screening is operational now. There is no public status page available as of now to check the status of the queue. It is monitored internally.

2. This issue happened in pilot environment only. Production environment is not impacted. The suggestion of sync screening was made, in case if the client's testing get impacted due to issue which had occurred.

Hope this clarifies your concern.