Limit number of concurrent executing actions (cloud & on-premise)
complete
R
Rick van den Dijssel
We would like to limit the number of concurrent executing actions on a Target Powershell session. With this we can use Powershell target connectors more easily with systems like SAP, Exchange, Skype and more. This because we limit the number of actions we therefore limit the number of active sessions to the external target system so we support all target systems which have a limit on the active open sessions.
In some cases this could help with overflow a system with api calls in x period because the amount of action overtime we can finish will be lower but this depends on the target system limitations. Becarefull that this isn't a solution for this last case (limited amount of api calls in a period) in some situations.
R
Rick van den Dijssel
marked this post as
complete
R
Rick van den Dijssel
marked this post as
planned
Due too a higher effort for maintaining provisioning and solving production issues besides some drawbacks in developing this feature we will not release this feature in the December release. The feature is now planned for January altough it's almost done we don't want to take the risk of releasing a not fully tested big change.
Planned January release
R
Rick van den Dijssel
marked this post as
under review
R
Rick van den Dijssel
marked this post as
in progress
R
Rick van den Dijssel
marked this post as
planned
Planned December release
R
Rick van den Dijssel
Due too a higher effort for maintaining provisioning and solving production issues besides some drawbacks in developing this feature we will not release this feature in the December release. The feature is now planned for January altough it's almost done we don't want to take the risk of releasing a not fully tested big change.
Planned January release
R
Rick van den Dijssel
marked this post as
under review
R
Rick van den Dijssel
Merged in a post:
Target PowerShell connector session management
G
Grady Koopman
R
Rick van den Dijssel
Merged in a post:
Target System Concurrent Session Limits
J
J. Anderson
With the Summer Rollover for Students, we ran into Google API Queries per Second quotas that caused some issues with Updates.
To prevent these kind of issues, it would be useful if we could set two additional limiters on Custom Target Systems:
1) Concurrent Session limit - This would be very useful for processing O365 Exchange Targets which only allow two open PowerShell connections.
2) Actions per Second - This would prevent any per second limits imposed by the target system.
More information about the Rate Limits and Quotas errors returned by Google can be found here:
Implementing the suggested Backoff approach might work, with the drawback of adding Delays in the Google logic. Thus the above request to be able to set the limit directly on the Target System itself.
E
Eddy Bakker
We have made a change in the business rules which results in 225 changes. Exchange accepts only 4 changes per session/connector. This results in days of handy work to start new session to complete the changes. This is not workable! Can this update be brought forward and rolled out in October?
R
Rick van den Dijssel
Eddy Bakker: If this feature is planned you'll be notified by email if you voted on this feature.
J
J. Anderson
Load More
→