This call automatically copies organization-level settings and config templates. It works fine for low number of config templates, but when the organization has more than 14-15 config templates, api call times out.
I have tried to clone an organizaton that has 25 config templates via the dashboard (and not via the api), and the operation succeeded in around 2 minutes. So indeed, looking like the time it takes for the clone to run is proportional to the number of config templates, and it can be done over the dashboard as they do not have a timeout there, but can't be done via the api because of the 60-second hard timeout.
I checked action batches as well but this operantion is not supported by action batches.
Any idea how we can make this work via the api, for organizations that have more then ~15 config templates?
yes this is sure it is not related to the time limit but need to figure out why your API call takes 60 minutes. Let me check if i can find anything related to this or if someone in my circle had this issue in past.
Even if I set single_request_timeout to 300 seconds or any other value, I get back a gateway error from the api after 60 seconds. That's probably where the hard limit is for the api, so we can not set it to a bigger value than 60 seconds.