Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Created by Guest
Created on Nov 4, 2020

Add Async/Await APIs to avoid thread pool exhaustion

Multiple interfaces within the product are forcing clients and partners to abandon proper async/await implementations because the product does not implement async itself.

This means that even if solutions properly implement async, they will eventually be forced to Wait the results of the call because S&N APIs do not support async.

Examples of such APIs are ISelectionFactory and ScheduleBase.Execute.

There are likely more areas of the API that require proper async implementations that should be resolved in order to mitigate risk of Thread Pool exhaustion.