Google Drive watch初始同步后无法触发回调的排查求助

背景信息 #

• 需求：企业用户指定文件夹收到新文件时，接收回调通知
• 已完成配置：创建服务账号并授予Google Drive Scope的域级权限
• 问题现象：调用files.watch或changes.watch接口时，仅收到初始sync回调，后续文件夹操作无update回调；此前代码正常接收大量update回调，周末后测试恢复正常
• 怀疑原因：开发测试期间注册过多通道，导致Google静默临时限制通道注册，无警告/错误返回，限制随周末过期自动解除
• 已提交Google官方Bug报告

相关代码片段 #

//Creating the credential
GoogleCredential credential = GoogleCredential.FromJson(credentialJson).CreateScoped(scopes).CreateWithUser(userToImpersonate);

//Creating the service
var service = new DriveService(new BaseClientService.Initializer()
{
    HttpClientInitializer = credential,
    ApplicationName = _configuration.ApplicationName
});


// Create a new watch request with an expiration time
// WatchChannelExpirationInMinutes = 300
Channel body = new Channel
{
    Id = Guid.NewGuid().ToString(),
    Type = "web_hook",
    Address = _configuration.CallbackUrl,
    Expiration = DateTimeOffset.UtcNow.AddMinutes(_configuration.WatchChannelExpirationInMinutes).ToUnixTimeMilliseconds()
};
// Find the user's folder to watch
var folderId = JGGoogleDriveDriver.FindFolderId(usernameToWatch, string.Empty, _configuration.UserFolderName); //This returns the correct folderId
             

// Set up the watch request on the folder
var request = service.Files.Watch(body, folderId);

Channel response = await request.ExecuteAsync();

//Log result - everything looks ok
_logger.LogInformation($"Files Watch channel ID: {response.Id} for username {usernameToWatch} - expires {(response.Expiration.HasValue ? $"on {DateTimeOffset.FromUnixTimeMilliseconds(response.Expiration.Value).ToString("yyyy-MM-dd HH:mm:ss")}" : "at an unknown time")}");

收到的sync回调头部信息 #

{
  "user-agent": "APIs-Google; (+https://developers.google.com/webmasters/APIs-Google.html)",
  "content-length": "0",
  "accept": "*/*",
  "accept-encoding": "gzip, deflate, br",
  "x-forwarded-for": "74.125.210.64",
  "x-forwarded-host": "<myserver.com>",
  "x-forwarded-proto": "https",
  "x-goog-channel-expiration": "Fri, 12 Jul 2024 22:47:59 GMT",
  "x-goog-channel-id": "2e322d09-d0f4-4ae3-9e20-aaaaaaaaaaaa",
  "x-goog-message-number": "1",
  "x-goog-resource-id": "aaaaaa-ielTQ5JGeHicJERaaaaa",
  "x-goog-resource-state": "sync",
  "x-goog-resource-uri": "https://www.googleapis.com/drive/v3/files/aaaaaaczeElbmNfWchnVrgDs4jraaaaaa?alt=json&null"
}

排查与解决方案方向 #

1. 通道生命周期管理
   • 测试阶段避免重复创建无意义的通道，每次创建新通道前调用Channels.Stop接口主动销毁旧通道（使用返回的channelId和resourceId）
   • 缩短测试用通道的过期时间，避免大量过期通道堆积
2. 请求合法性校验
   • 确认回调地址可以正常接收POST请求，无防火墙/负载均衡拦截
   • 校验回调请求的x-goog-resource-state字段，确保没有遗漏update状态的请求
3. 活跃通道查询
   • 目前Google Drive API没有直接查询活跃通道数量的接口，可通过以下方式间接统计：
     • 本地日志记录所有创建的通道ID和过期时间，定期清理已过期的记录
     • 调用Channels.Stop时记录成功/失败状态，推断活跃通道情况
4. 限制规避
   • 若怀疑是临时限制，可分批次创建通道，避免短时间内大量请求
   • 使用同一个通道ID复用监听（若业务允许），减少通道创建频率

内容的提问来源于stack exchange，提问作者Eduardo Poças