Issue Summary

Attempting to push new members to related Program teams from Portfolio, gives 'Internal server error'

The customer used the Portfolio slide out > Members tab and clicked on the button Push Members to related Program teams. This gave an 'internal server error'. When it happened, it was observed it failed multiple times for this specific portfolio and it finally worked later, looks like it was timing out with the size of the payload in the request.

There were 244 Members that had to be added to the related program teams from that Portfolio when that error occurred.

It seems that the number of users to push is related to this performance issue so trying to add 100+ or 200+ users seems to create this issue behavior. 

Steps to Reproduce

1. Navigate to a  Portfolio slide out > Members tab
2. Make sure to have  200+ users to push
3. Click on the button Push Members to related Program teams
4. Observe Server error

Expected Results

There should not be any error or performance issue

Actual Results

There seems to be a performance issue. It seems that the number of users to push is related to this performance issue.

In the ASP log, there is 'Script timed out' errors on "error_file":"/AddProgram.asp" which seems to be a relevant page here

{"timestamp":"2023-07-21T13:06:36.820000-04:00","version":"10.120.2.30336","log_type":"exception","correlationid":"gP4wgvPDJi3iu8qoNgQEyPHV+K6DTOL15MsbIbf0hLc=","logfrom_location":"Website-ASP","customer_db":"AgileCraft_xxxx","user":"13947","url":"https:\/\/xxx:443\/AddProgram.asp","urlverb":"POST","ASP_function":"Error.asp","PageName":"Portfolios","ErrorId":"4148","error_number":"-2147467259","error_description":"Script timed out","error_source":"","error_file":"\/AddProgram.asp","error_line":"0","error_column":"-1","error_category":"Active Server Pages","error_aspdescription":"The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.","error_aspcode":"ASP 0113"} 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available