Your inquiry mentions the use of Chrome driver to upload files to a remote server, noting that this process can sometimes exceed 30 minutes. You attempted to increase the page load timeout value with the following code snippet:
driver.Manage().Timeouts().PageLoad = TimeSpan.FromSeconds(3600);
It's important to acknowledge that the combination of ChromeDriver and Chrome is not yet fully W3C compliant, potentially causing deviations from your intended configuration. Comparatively, GeckoDriver appears to align better with W3C standards. Here are the default timeout settings for GeckoDriver:
implicit: 0pageLoad: 300000script: 30000
While crafting your Automation Scripts, you have the flexibility to override these default timeout settings for each WebDriver instance, just like how you did in the provided code block.
driver.Manage().Timeouts().PageLoad = TimeSpan.FromSeconds(3600);
According to the current WebDriver W3C Candidate Recommendation, the maximum safe integer value for timeouts is defined as Number.MAX_SAFE_INTEGER (9007199254740991).
Note: It's not recommended to solely rely on increasing the page load timeout when waiting for file uploads to a remote server. Creating a logic to determine completion of File Upload would be a more appropriate programming practice, though it falls beyond the scope of this discussion.