Why is this setting causing the POST /api/v2/recording/search data action to fail with a 504 Gateway Timeout when pushing to AWS S3? The chain of custody requirements mandate a specific metadata payload, but the integration breaks after 30 seconds on large digital channel batches. Using Architect v2.0 with s3_integration enabled in London region.