vanderbilt-redcap / cross-project-piping-module

Cross-Project Piping pipes from one field in one project into another field in another project. This project does not currently have a support budget that allows responses to issues.
MIT License
10 stars 7 forks source link

IP banned when piping for many records #15

Open mschulze0 opened 2 years ago

mschulze0 commented 2 years ago

Hi,

we have a problem with IPs getting banned by REDCap when we cross-pipe many records and many fields because of too many API requests per minute. Maybe you could introduce a sleep function for these cases (that can be optionally enabled via a module setting)?

mmcev106 commented 2 years ago

Refactoring the module so that the piping occurred on the backend rather than the front-end would also likely fix this, and have other benefits.

carlreedw commented 2 years ago

@mschulze0 Is this happening when you use the 'Pipe All' button? Or when piping via the Data Entry page?

Currently, the former pipes via the server but Data Entry piping was written long ago and uses the browser/front-end.

I will talk with the client currently funding my work on this module to see if they would like for me to investigate.