[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:checks-before-retrying-automated-proxy-request":3,"blog-article:\u002Fblog\u002Fchecks-before-retrying-automated-proxy-request":1114,"blog-related:\u002Fblog\u002Fchecks-before-retrying-automated-proxy-request":1115,"blog-translations:\u002Fblog\u002Fchecks-before-retrying-automated-proxy-request":1116},{"available":4,"article":5,"relatedArticles":231,"translations":966},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":230},"strapi",4545,"zsa9y1lbxyqwhm1qe3c307s1","zh","checks-before-retrying-automated-proxy-request","\u002Fblog\u002Fchecks-before-retrying-automated-proxy-request","自动化任务重试代理请求前要检查什么","重试代理 IP 请求之前要确认四件事：错误能不能重试、动作重放会不会重复、站点规则允不允许、这次重试会不会把预算用光。四项有一项不确定，就不该自动重试。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_fda55f579d.webp","2026-11-19T03:27:53.882Z","2026-11-19T03:27:53.861Z","Global Proxies Team",[],false,0,3,"blocks",[24,30,34,40,44,48,52,64,68,72,89,93,97,102,106,110,121,125,129,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"自动化任务里，\"重试\"是最容易被写成默认动作的一步。代理 IP 请求失败就重试，看起来省事，实际上把判断责任推给了下一个失败。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"重试一个代理 IP 请求之前至少有四件事要确认：这个错误能不能重试、这个操作重放一次会不会重复、站点规则允不允许、这次重试会不会把预算用光。四项里有一项不确定，就不该自动重试。",{"type":35,"level":36,"children":37},"heading",2,[38],{"text":39,"type":29},"自动重试前，先判断错误类型和是否可以重试",{"type":35,"level":21,"children":41},[42],{"text":43,"type":29},"连接错误只有在操作幂等时才适合重试",{"type":25,"children":45},[46],{"text":47,"type":29},"连接超时或连接重置有时可以重试，但应先确认请求是否可能已到达目标端，并确认操作具备幂等性。DNS 解析失败则先排查解析和网络状态，不应一概按同一策略重试。",{"type":35,"level":21,"children":49},[50],{"text":51,"type":29},"认证失败和请求参数错误不应自动重试",{"type":25,"children":53},[54,56,62],{"text":55,"type":29},"先识别 401（未认证）或 407（代理认证）由哪一层返回，并检查相应挑战信息。客户端支持的正常认证协商，或接口明确支持的凭据刷新，可在受控预算内处理；相同无效凭据不得循环重试，持续失败应停止并人工核对。HTTP 对 401\u002F407 的定义见 ",{"text":57,"type":29,"marks":58},"RFC 9110 第 11、15.5.2 与 15.5.8 节",[59],{"href":60,"type":61},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9110.html","link",{"text":63,"type":29},"。",{"type":25,"children":65},[66],{"text":67,"type":29},"业务类错误不可重试：400、422 说明请求本身有问题，改参数才有意义。",{"type":35,"level":21,"children":69},[70],{"text":71,"type":29},"遇到限流、5xx 或未知错误时分别如何处理",{"type":25,"children":73},[74,76,81,83,88],{"text":75,"type":29},"遇到 429，先按服务端给出的等待信息暂停。429 表示给定时间内请求过多（",{"text":77,"type":29,"marks":78},"RFC 6585 第 4 节",[79],{"href":80,"type":61},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc6585#section-4",{"text":82,"type":29},"）；等待后是否重试，还要确认请求仍符合目标站规则和任务预算，不要按固定间隔反复发送。具体暂停与恢复思路可参考",{"text":84,"type":29,"marks":85},"采集任务遇到 429 后如何暂停和恢复",[86],{"href":87,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002F429-how-long-before-next-request",{"text":63,"type":29},{"type":25,"children":90},[91],{"text":92,"type":29},"5xx 可能表示暂时故障，也可能发生在目标端已执行、但响应未能正常返回之后。未确认接口语义前，应先查询处理结果或转人工核对，再决定是否重试。",{"type":25,"children":94},[95],{"text":96,"type":29},"未知错误一律不自动重试。未知意味着\"重放后果不明\"，这类情况应该停下来记录，而不是交给重试逻辑。",{"type":98,"children":99},"code",[100],{"text":101,"type":29},"| 错误类型 | 可否自动重试 | 额外条件 | 建议动作 |\n| --- | --- | --- | --- |\n| 连接超时、连接重置 | 可以 | 操作幂等 | 按退避重试，计入预算 |\n| 401、407 | 视响应来源和认证流程判断 | 仅限受支持的认证协商或明确允许的凭据刷新 | 识别返回方与挑战；相同无效凭据停止并转人工 |\n| 400、422 | 不可以 | — | 停止，修请求 |\n| 429 | 暂停后可受控复测 | 等待要求已满足；已核对原操作结果或幂等保护，并确认重试预算 | 确认允许恢复后最多复测一次；无等待依据时先查官方规则或授权方 |\n| 5xx（语义未确认时的保守默认） | 暂不自动重试 | 先确认操作是否幂等、目标端是否可能已处理 | 核实接口语义与任务状态后再决定 |\n| 未知 | 不可以 | — | 记录并转人工 |",{"type":35,"level":36,"children":103},[104],{"text":105,"type":29},"重放代理请求前，先确认重复执行会产生什么结果",{"type":25,"children":107},[108],{"text":109,"type":29},"判断幂等性，看的是\"同样的请求执行两次，结果是否等价\"，而不是\"代码里有没有写重试\"。",{"type":25,"children":111},[112,114,119],{"text":113,"type":29},"GET、HEAD 通常用于读取，但仍需遵守目标站频率限制。PUT、DELETE 在协议语义上通常设计为幂等，具体接口仍可能触发审计或覆盖更新，应以接口文档和业务语义为准（HTTP 方法的幂等定义见 ",{"text":115,"type":29,"marks":116},"RFC 9110 第 9.2.2 节",[117],{"href":118,"type":61},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9110#section-9.2.2",{"text":120,"type":29},"）。",{"type":25,"children":122},[123],{"text":124,"type":29},"POST 通常不保证幂等。创建订单、提交表单或发起支付前，应先确认目标端是否已处理；支持幂等键时，按接口要求复用同一个键。",{"type":25,"children":126},[127],{"text":128,"type":29},"判断方法很具体：问一句\"如果这个请求其实已经成功了，再发一次会发生什么\"。答不上来，就按不可重试处理。",{"type":25,"children":130},[131,133,138],{"text":132,"type":29},"如果目标站支持幂等键（同一键重复提交只生效一次），POST 也能变成可判定的重试：每次尝试带同一个键，重放后查回执，而不是靠\"感觉没成功\"再发一遍。切换出口后的状态核对，可参考",{"text":134,"type":29,"marks":135},"切换代理 IP 出口后如何确认业务状态正常",[136],{"href":137,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-egress-switch-regression-testing",{"text":139,"type":29},"。没有这个条件，宁可停下来查，不要自动重试。",{"type":35,"level":36,"children":141},[142],{"text":143,"type":29},"遵守目标站规则，避免对拒绝或限流请求反复重试",{"type":25,"children":145},[146],{"text":147,"type":29},"有三类重试应直接停止：收到 403、验证码或明确访问限制后继续发送；超过目标站公开频率后仍不断重放；没有次数、时长和并发上限地持续重试。它们的共同问题是继续发送会放大限制、重复执行或资源消耗，而不是解决故障。",{"type":25,"children":149},[150],{"text":151,"type":29},"判断边界时以目标站公开的规则、接口文档与授权范围为准；拿不到明确说法时，取更保守的那一档。",{"type":35,"level":36,"children":153},[154],{"text":155,"type":29},"如何设置重试次数、总时长和并发上限",{"type":25,"children":157},[158],{"text":159,"type":29},"预算要同时定三个上限：单条请求的次数、一轮任务的总时长、同时在跑的并发。",{"type":25,"children":161},[162],{"text":163,"type":29},"次数上限决定\"最多试几次\"，时长上限决定\"最多耗多久\"，并发上限决定\"失败时会不会一起涌上去\"。三者缺一，重试就会在失败时放大流量。",{"type":25,"children":165},[166],{"text":167,"type":29},"退避的作用是错开重试时间，不是缩短等待。需要加抖动时只往上限方向加，实际间隔不得短于对方要求的等待下限。",{"type":25,"children":169},[170],{"text":171,"type":29},"预算用尽后的动作要预先定义：标记失败、转人工、还是等下一轮。最常见的问题是预算用尽后悄悄放弃，任务看起来成功了，实际漏了一批。",{"type":35,"level":36,"children":173},[174],{"text":175,"type":29},"每次重试都应记录哪些决策和结果",{"type":25,"children":177},[178],{"text":179,"type":29},"每次重试至少记五项：任务 ID、尝试序号、错误码、决策（重试\u002F停止\u002F转人工）、结果。缺了\"决策\"这一项，事后只能看到一堆失败，看不出当时为什么继续。",{"type":25,"children":181},[182],{"text":183,"type":29},"记录还要能回答一个问题：这一轮的重试，是程序自己决定的，还是人手工触发的。两者的责任与复盘方式不同。",{"type":35,"level":36,"children":185},[186],{"text":187,"type":29},"常见问题",{"type":35,"level":21,"children":189},[190],{"text":191,"type":29},"重试次数要不要按接口分开设？",{"type":25,"children":193},[194],{"text":195,"type":29},"要。读接口与写接口的幂等风险不同，用同一上限会把写接口的风险放大。",{"type":35,"level":21,"children":197},[198],{"text":199,"type":29},"429 没给 Retry-After 怎么办？",{"type":25,"children":201},[202],{"text":203,"type":29},"按接口文档或错误正文找等待依据。都找不到就暂停转人工，别按固定间隔硬撞。",{"type":35,"level":21,"children":205},[206],{"text":207,"type":29},"换一个代理 IP 重试，算不算新请求？",{"type":25,"children":209},[210],{"text":211,"type":29},"在目标站看来通常是新请求，仍可能计入同一账号或同一站点的限额，也可能触发风控。不能用来绕开限制。",{"type":35,"level":21,"children":213},[214],{"text":215,"type":29},"只读接口也需要预算吗？",{"type":25,"children":217},[218],{"text":219,"type":29},"需要。读接口虽幂等，同样会触发频率限制；预算按请求量算，不按风险算。",{"type":25,"children":221},[222,224,229],{"text":223,"type":29},"账号与接入问题可查看",{"text":225,"type":29,"marks":226},"帮助中心",[227],{"href":228,"type":61},"https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F",{"text":63,"type":29},"",[232,475,696],{"source":6,"id":233,"documentId":234,"translationKey":234,"locale":9,"slug":235,"path":236,"_path":236,"title":237,"description":238,"excerpt":238,"image":239,"publishedAt":240,"updatedAt":241,"author":17,"tags":242,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":243,"bodyHtml":230},4550,"gqryzu9nle8pzuzfzsq99ca4","mobile-proxy-troubleshooting-log-fields","\u002Fblog\u002Fmobile-proxy-troubleshooting-log-fields","移动端代理问题需要收集哪些日志信息","代理 IP 排障日志的价值在于别人能否按同一条件复现。按必须、可选、禁止三档收字段，导出前删掉凭据与个人标识，再按时间和设备命名打包，缺一项就补一项。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_47c42e5b14.webp","2026-11-19T03:28:14.371Z","2026-11-19T03:28:14.354Z",[],[244,248,252,256,267,271,275,279,283,287,291,295,299,303,357,367,371,382,386,390,394,398,421,425,428,432,436,440,444,448,452,456,460,464,468],{"type":25,"children":245},[246],{"text":247,"type":29},"排障日志的价值不在多，而在\"别人能不能按同一条件复现\"。手机端尤其容易丢信息：系统日志滚动快、应用日志分散，连接记录也可能包含账号标识或认证信息，导出前应先检查并脱敏。",{"type":25,"children":249},[250],{"text":251,"type":29},"先按\"必须、可选、禁止\"列出字段，收集后检查敏感信息，再按时间和设备命名打包。这样既方便排查，也能减少凭据或个人信息外泄。",{"type":35,"level":36,"children":253},[254],{"text":255,"type":29},"移动端代理故障日志需要记录哪些关键信息",{"type":25,"children":257},[258,260,265],{"text":259,"type":29},"最小记录集合应包含：时间（含时区）、网络类型、目标地址与协议、错误类型或状态码、出口地区、客户端版本、设备与系统版本、失败阶段、观察来源、复现步骤，以及事件／请求关联 ID；没有服务端 ID 时可用受控的 caseID。出口保留地区和同一审查范围内稳定化名，不要求公开真实 IP。若错误表现为连接重置，可参照",{"text":261,"type":29,"marks":262},"代理连接被重置要记录哪些证据",[263],{"href":264,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-connection-reset-evidence-record",{"text":266,"type":29},"补齐时间、错误码和链路记录。",{"type":25,"children":268},[269],{"text":270,"type":29},"时间和时区用于对齐事件，网络类型用于区分蜂窝与 Wi-Fi，目标地址和错误信息有助判断影响范围，复现步骤则决定接手人员能否重现现场。缺少关键字段会增加排查难度；暂时无法提供时，应标明缺失项，而不是用猜测补齐。",{"type":25,"children":272},[273],{"text":274,"type":29},"这些字段里最容易被忽略的是“出口地区”。同样一条失败记录，出口在国内和出口在新加坡，指向的原因完全不同。记录时写地区即可，不需要写完整 IP。",{"type":35,"level":36,"children":276},[277],{"text":278,"type":29},"哪些日志字段有助排查，哪些信息必须删除或脱敏",{"type":98,"children":280},[281],{"text":282,"type":29},"| 档位 | 字段 | 来源 | 说明 |\n| --- | --- | --- | --- |\n| 必须 | 时间与时区、网络类型、目标域名与协议、错误码或错误类型、出口地区或稳定化名、客户端与 App 构建版本、设备与系统版本、失败阶段、观察来源、事件／请求关联 ID（无服务端 ID 时用受控 caseID）、复现步骤 | 系统设置、客户端、目标站回显 | 网络类型只列一次；记录是否发生切换，发生时填写时间，未发生或未知也明确标出 |\n| 可选 | 信号强度、应用前后台状态、同一时段另一台设备的对照结果 | 系统状态、现场观察 | 按问题类型取舍；网络切换事件统一记在必填项中 |\n| 禁止 | Cookie、Authorization、完整查询串、手机号与邮箱、设备唯一标识、精确位置 | 应用日志、请求记录 | 导出前必须删除或替换 |",{"type":25,"children":284},[285],{"text":286,"type":29},"必填项应按表格逐项记录，其中“复现步骤”常被漏掉，却是他人还原问题的重要依据。",{"type":25,"children":288},[289],{"text":290,"type":29},"分档的意义是防止两种极端：一种是只发一句\"连不上\"，另一种是把整个日志包原样发出去。前者无法排查，后者泄露风险。",{"type":25,"children":292},[293],{"text":294,"type":29},"可选字段按问题类型补充：怀疑网络切换时，记录切换时间；怀疑后台限制时，补充应用前后台状态。",{"type":35,"level":36,"children":296},[297],{"text":298,"type":29},"导出日志前，先删除或遮盖这六类敏感信息",{"type":25,"children":300},[301],{"text":302,"type":29},"导出前重点检查六类信息：",{"type":304,"format":305,"children":306},"list","unordered",[307,317,325,333,341,349],{"type":308,"children":309},"list-item",[310,315],{"text":311,"type":29,"marks":312},"认证凭据",[313],{"type":314},"bold",{"text":316,"type":29},"：Cookie、Authorization 头、API Key 和客户端令牌，泄露后可能被用于访问账号。",{"type":308,"children":318},[319,323],{"text":320,"type":29,"marks":321},"完整查询串",[322],{"type":314},{"text":324,"type":29},"：保留必要路径，去掉参数中的会话 ID、用户 ID 和签名，凭据和身份值应删除或用稳定占位符替代；经核对不敏感且有助复现的排序、分页和地区参数值可以保留。不能共享真实值时，提供等价虚构示例并标明替代关系。",{"type":308,"children":326},[327,331],{"text":328,"type":29,"marks":329},"个人标识",[330],{"type":314},{"text":332,"type":29},"：手机号、邮箱、姓名和身份证件号。",{"type":308,"children":334},[335,339],{"text":336,"type":29,"marks":337},"设备唯一标识",[338],{"type":314},{"text":340,"type":29},"：广告标识、硬件序列号和安装 ID。",{"type":308,"children":342},[343,347],{"text":344,"type":29,"marks":345},"精确位置",[346],{"type":314},{"text":348,"type":29},"：经纬度和详细地址；通常只需保留城市或地区。",{"type":308,"children":350},[351,355],{"text":352,"type":29,"marks":353},"业务敏感数据",[354],{"type":314},{"text":356,"type":29},"：订单内容、聊天记录和上传文件内容；排障通常只需要记录请求类型，不需要保留具体内容。",{"type":25,"children":358},[359,361,366],{"text":360,"type":29},"替换方式要统一：用 `[REDACTED]` 或 `***` 替换凭据与身份值，不保留原值长度等可能暴露特征的信息；同时保留经核对不敏感、复现所必需的排序、分页和地区参数。无法共享真实参数时，提供等价虚构示例并说明替代关系。也不要整段删除，否则看不出请求结构。日志该记录什么、不该记录什么，可对照 ",{"text":362,"type":29,"marks":363},"OWASP 日志记录速查表",[364],{"href":365,"type":61},"https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FLogging_Cheat_Sheet.html",{"text":63,"type":29},{"type":35,"level":36,"children":368},[369],{"text":370,"type":29},"如何命名和打包日志，方便按时间定位问题",{"type":25,"children":372},[373,375,380],{"text":374,"type":29},"一个包只放一次复现：时间范围、设备、版本写在文件名里，例如\"时间范围-设备型号-系统版本-问题类型\"。包内附一份清单，说明每个文件对应哪一段操作。整理完成后，可按",{"text":376,"type":29,"marks":377},"代理网络故障如何制作最小复现记录",[378],{"href":379,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-fault-minimal-reproduction-record",{"text":381,"type":29},"检查现场是否可复现。",{"type":25,"children":383},[384],{"text":385,"type":29},"不要把几天的日志混在一个包里。时间跨度越大，定位越慢，也越容易把无关的账号信息带进去。",{"type":25,"children":387},[388],{"text":389,"type":29},"文件格式优先用原始文本或结构化导出，不要只发截图。截图可以作为补充，但不能替代原始记录——时间精度和字段完整性都会丢。",{"type":25,"children":391},[392],{"text":393,"type":29},"如果必须发截图，先检查状态栏、通知、账号头像、地址栏这些位置，它们经常带着身份信息。",{"type":35,"level":36,"children":395},[396],{"text":397,"type":29},"提交日志前，用五个问题检查材料是否完整",{"type":304,"format":399,"children":400},"ordered",[401,405,409,413,417],{"type":308,"children":402},[403],{"text":404,"type":29},"别人拿着这份日志，能不能按写下的步骤复现一次？",{"type":308,"children":406},[407],{"text":408,"type":29},"时间是否带时区，是否与目标站记录能对上？",{"type":308,"children":410},[411],{"text":412,"type":29},"有没有哪一处还能看出账号、令牌或个人信息？",{"type":308,"children":414},[415],{"text":416,"type":29},"目标地址是否保留了域名和协议，去掉了敏感参数？",{"type":308,"children":418},[419],{"text":420,"type":29},"失败前后是否各留了一段观察窗口，而不是只有一条错误？",{"type":25,"children":422},[423],{"text":424,"type":29},"五个问题里有一个答不上来，就先补齐再提交。补齐的成本，通常比来回追问低。",{"type":35,"level":36,"children":426},[427],{"text":187,"type":29},{"type":35,"level":21,"children":429},[430],{"text":431,"type":29},"代理 IP 的日志可以整包发给支持方吗？",{"type":25,"children":433},[434],{"text":435,"type":29},"不建议。按时间窗截取，附本机时间与时区；整包既慢又扩大泄露面。",{"type":35,"level":21,"children":437},[438],{"text":439,"type":29},"截图里哪些信息必须打码？",{"type":25,"children":441},[442],{"text":443,"type":29},"头像、昵称、手机号、通知内容、地址栏参数、设备名称都要打码。只提供定位问题所需的最少信息。",{"type":35,"level":21,"children":445},[446],{"text":447,"type":29},"代理 IP 的主机和端口要不要一起提供？",{"type":25,"children":449},[450],{"text":451,"type":29},"默认先脱敏。确有排查需要时，只通过受控支持渠道按需提供，并限定访问范围与保留期限；账号、密码、令牌、签名及其他可用于认证的凭据必须遮盖。",{"type":35,"level":21,"children":453},[454],{"text":455,"type":29},"时间用本地时区还是 UTC？",{"type":25,"children":457},[458],{"text":459,"type":29},"都行，写明是哪一个并全篇统一。与目标站记录对照时换算到同一时区。",{"type":35,"level":21,"children":461},[462],{"text":463,"type":29},"工单里要不要附完整日志包？",{"type":25,"children":465},[466],{"text":467,"type":29},"先附最小复现包和清单，对方要哪段再补。一次给全反而难定位。",{"type":25,"children":469},[470,471,474],{"text":223,"type":29},{"text":225,"type":29,"marks":472},[473],{"href":228,"type":61},{"text":63,"type":29},{"source":6,"id":476,"documentId":477,"translationKey":477,"locale":9,"slug":478,"path":479,"_path":479,"title":480,"description":481,"excerpt":481,"image":482,"publishedAt":483,"updatedAt":484,"author":17,"tags":485,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":486,"bodyHtml":230},4549,"sbks9w6bc9gtratt9p27x35c","mobile-signal-fluctuation-vs-proxy-disconnect","\u002Fblog\u002Fmobile-signal-fluctuation-vs-proxy-disconnect","移动网络波动时如何区分代理断线与信号问题","移动网络波动与代理 IP 连接异常都可能导致请求失败。通过时间线对照网络切换、代理握手和目标站响应，判断下一步应检查接入网络、代理连接还是目标服务。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_4c3f4f8011.webp","2026-11-19T03:28:10.618Z","2026-11-19T03:28:10.598Z",[],[487,491,495,499,503,507,511,515,519,523,527,531,535,539,543,589,593,597,601,615,623,631,635,639,643,647,651,654,658,662,666,670,674,678,682,686],{"type":25,"children":488},[489],{"text":490,"type":29},"在地铁、电梯或人流密集处，手机请求失败很常见。这时代理 IP 断了和手机网络本身不稳，给出的现象几乎一样：转圈、超时、应用提示网络错误，只看一次失败分不出是哪一层。",{"type":25,"children":492},[493],{"text":494,"type":29},"先把网络切换、信号变化、代理连接和请求结果记在同一条时间线上。若换网络后问题消失，说明接入网络或对应配置可能相关；若问题持续存在，还要检查代理连接、认证、DNS 和目标站响应，不能只据此归因于代理侧。",{"type":35,"level":36,"children":496},[497],{"text":498,"type":29},"如何区分请求未发出和代理请求未收到响应",{"type":25,"children":500},[501],{"text":502,"type":29},"请求失败大致有两种情况：一种是尚未获得目标站的有效响应，例如域名解析失败、到代理入口的 TCP 连接未建立或 TLS 握手失败；这些现象可能发生在不同链路环节，需结合解析结果、连接目标和代理日志定位。另一种是连接已经建立，但等待响应时超时或中途被重置；此时目标站可能已经收到并处理请求，客户端却只看到超时，因此不能把“未收到响应”直接当作“目标端未执行”。",{"type":25,"children":504},[505],{"text":506,"type":29},"遇到 401、403、429 或验证码页面，先确认响应来源和失败阶段；按认证、限流或目标站规则处理，不把状态码本身当成信号或代理故障证据。",{"type":25,"children":508},[509],{"text":510,"type":29},"区分前两类，看三个地方：客户端有没有\"已连接\u002F已发送\"的记录；有没有收到状态码；错误是立刻出现还是等了一段时间才出现。三个都指向\"没发出去\"，就先按链路查；有\"已发送\"却无响应，才需要区分网络波动与代理断线。",{"type":35,"level":36,"children":512},[513],{"text":514,"type":29},"按时间线对照移动网络变化与代理连接状态",{"type":25,"children":516},[517],{"text":518,"type":29},"时间线只需要三个来源：系统网络状态（蜂窝或 Wi-Fi、切换时刻、飞行模式开关）、代理客户端的连接与认证事件（已连接、重连、认证失败）、请求本身（开始时间、错误类型、恢复时间）。三者用同一台设备的时钟记录，精确到秒，不要混用服务器时间。",{"type":25,"children":520},[521],{"text":522,"type":29},"记录的要求不是\"记得多\"，而是\"失败时刻前后各留一段观察窗口\"，长度按自己的任务节奏定。窗口里有切换事件、有重连事件、有请求结果，才谈得上判读。",{"type":25,"children":524},[525],{"text":526,"type":29},"下表为示例时间线，时间、状态码、信号格数和事件均为虚构，仅用于说明记录方式，不代表实测结果。",{"type":98,"children":528},[529],{"text":530,"type":29},"| 时间 | 网络类型与信号 | 是否发生切换 | 代理连接事件 | 请求结果 | 备注 |\n| --- | --- | --- | --- | --- | --- |\n| 09:12:03 | 蜂窝，2 格 | 否 | 已连接，出口 A | 200 | 基线条件 |\n| 09:14:20 | 蜂窝，1 格 | 否 | 已连接 | 请求超时 | 同时段另一台设备也超时 |\n| 09:15:02 | Wi-Fi | 是，蜂窝→Wi-Fi | 重连一次后已连接 | 200 | 切换后恢复 |\n| 09:18:40 | 蜂窝，3 格 | 是，Wi-Fi→蜂窝 | 重连中 | 连接被重置 | 在切换瞬间发起请求 |",{"type":25,"children":532},[533],{"text":534,"type":29},"表中六列是现场速记，够用来判断\"失败跟谁同时发生\"；要下结论还得补齐另外四项：目标 URL 与协议、状态码、出口地区、恢复动作。缺这四项，复测时无法确认第二次失败和第一次是不是同一件事。",{"type":25,"children":536},[537],{"text":538,"type":29},"一次只改一个变量：要判断切换的影响，就别同时换地点、换客户端版本、换目标域名。否则时间线再细，也只能说明\"当时确实失败了\"。",{"type":35,"level":36,"children":540},[541],{"text":542,"type":29},"对照网络切换、代理握手、信号强度和目标站响应",{"type":304,"format":305,"children":544},[545,553,561,575],{"type":308,"children":546},[547,551],{"text":548,"type":29,"marks":549},"切换",[550],{"type":314},{"text":552,"type":29},"：失败是否集中在网络切换后的短时间内。切换会重建路由和连接，这个窗口内的失败不能直接算到代理头上。",{"type":308,"children":554},[555,559],{"text":556,"type":29,"marks":557},"代理握手",[558],{"type":314},{"text":560,"type":29},"：客户端是否显示已连接、认证是否成功、有没有反复重连。认证失败、频繁重连更偏代理侧；一直显示已连接但请求不通，则要往下看目标响应。",{"type":308,"children":562},[563,567,569,574],{"text":564,"type":29,"marks":565},"信号强度",[566],{"type":314},{"text":568,"type":29},"：系统给的格数只是粗粒度值，格数下降说明无线环境变差，不等于数据连接一定不可用。它能提示\"该看网络侧了\"，不能单独作为结论。Android 上信号等级的含义见 ",{"text":570,"type":29,"marks":571},"SignalStrength 文档",[572],{"href":573,"type":61},"https:\u002F\u002Fdeveloper.android.google.cn\u002Freference\u002Fandroid\u002Ftelephony\u002FSignalStrength",{"text":63,"type":29},{"type":308,"children":576},[577,581,583,588],{"text":578,"type":29,"marks":579},"目标响应",[580],{"type":314},{"text":582,"type":29},"：有没有状态码、是不是只有某一个域名失败、换一个目标域名是否正常。只有一个域名失败，问题更可能在目标站或解析，而不是整条链路。连续断连的定位思路可参考",{"text":584,"type":29,"marks":585},"代理 IP 间歇性断开如何定位",[586],{"href":587,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-intermittent-disconnect-diagnosis",{"text":63,"type":29},{"type":25,"children":590},[591],{"text":592,"type":29},"顺序上先看切换，再看代理握手：这两项在本地就有记录，几秒内能确认。信号强度放在第三位，它只提示该看网络侧；目标响应放最后，因为要换域名复测，成本最高。",{"type":25,"children":594},[595],{"text":596,"type":29},"这四项记录用于缩小故障范围：切换和握手可说明连接状态，信号强度只能作为网络侧线索，目标响应则帮助确认失败阶段。结合同一请求 ID、网络事件和错误信息再进一步判断；认证失败或频繁重连都不能单独证明故障来自代理。证据不足时写“倾向”或“暂无法区分”。",{"type":35,"level":36,"children":598},[599],{"text":600,"type":29},"根据测试结果判断应排查移动网络还是代理连接",{"type":25,"children":602},[603,607,609,614],{"text":604,"type":29,"marks":605},"更像接入网络问题",[606],{"type":314},{"text":608,"type":29},"：失败反复出现在网络切换或弱信号时段，且相同代理在其他网络下可正常连接。可固定目标和配置复测，并检查 DNS、网络切换时机与客户端超时设置；这些现象是判断线索，不能单独证明故障来源。如果客户端显示在线但请求仍超时，可对照",{"text":610,"type":29,"marks":611},"客户端显示在线但请求超时",[612],{"href":613,"type":61},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-client-online-but-request-timeout",{"text":63,"type":29},{"type":25,"children":616},[617,621],{"text":618,"type":29,"marks":619},"更像代理连接问题",[620],{"type":314},{"text":622,"type":29},"：不同接入网络下都无法完成代理握手，且代理后台没有成功连接记录。此时可核对地址、端口、认证信息和服务状态；若代理连接已建立，则继续依据目标站响应排查。",{"type":25,"children":624},[625,629],{"text":626,"type":29,"marks":627},"无法区分",[628],{"type":314},{"text":630,"type":29},"：两层同时异常，或者观察窗口里既没有切换也没有重连记录。这时缩小变量——固定一个网络、只发一个请求、只打一个域名——再复测一次，不要在这个状态下下结论。",{"type":25,"children":632},[633],{"text":634,"type":29},"常见分支：只有某个 App 失败，先怀疑应用侧的代理支持差异；只有某个域名失败，先查目标站与解析；所有请求都失败且客户端显示离线，先查客户端与账号。这三种情况都不适合用\"换一批 IP 试试\"开始诊断，换 IP 会把现场清掉，下一次复现又要从头来。",{"type":35,"level":36,"children":636},[637],{"text":638,"type":29},"记录复测条件，避免用一次失败下结论",{"type":25,"children":640},[641],{"text":642,"type":29},"最小记录集合包括：测试时间、网络类型与信号、是否切换、代理连接事件、目标 URL、协议、状态码、出口地区、恢复动作、复测结果。缺了\"时间、网络、目标、结果\"四项，记录就无法复现。",{"type":25,"children":644},[645],{"text":646,"type":29},"复测尽量保持地点、网络类型、目标和时段一致，并记录观察窗口与样本范围。有限样本只能说明这几次的表现。结果不一致可能来自环境变化、间歇故障或目标变化，应保留各次记录并标为“待复测”。",{"type":25,"children":648},[649],{"text":650,"type":29},"停止条件也要提前定：按事先定好的次数跑完、结果一致就停；出现账号异常、验证码或需要重新认证时立即停止，不要为了追求样本量反复切网。整个过程只用自有或获授权设备，日志导出前先脱敏。",{"type":35,"level":36,"children":652},[653],{"text":187,"type":29},{"type":35,"level":21,"children":655},[656],{"text":657,"type":29},"开关一次飞行模式，能当代理 IP 断线的复现手段吗？",{"type":25,"children":659},[660],{"text":661,"type":29},"能当一次\"网络重建\"。但它同时改注册网络、连接与代理会话，只能证明重建后是否恢复。",{"type":35,"level":21,"children":663},[664],{"text":665,"type":29},"同一代理 Wi-Fi 正常、蜂窝失败，先查哪边？",{"type":25,"children":667},[668],{"text":669,"type":29},"先对照蜂窝与 Wi-Fi 下的网络类型、代理配置和连接记录，再检查运营商覆盖及客户端是否为不同网络分别保存了代理设置。",{"type":35,"level":21,"children":671},[672],{"text":673,"type":29},"手机读不到信号强度，时间线还成立吗？",{"type":25,"children":675},[676],{"text":677,"type":29},"成立。用网络类型变化、切换时刻、能否解析与建连替代，格数只作参考。",{"type":35,"level":21,"children":679},[680],{"text":681,"type":29},"同事的设备能连、我的不能，算代理问题吗？",{"type":25,"children":683},[684],{"text":685,"type":29},"先确认两台是否同一出口、同一目标、同一时段。三项有一项不同，就不能对比。",{"type":25,"children":687},[688,690,695],{"text":689,"type":29},"需要查具体接入入口时，可查看",{"text":691,"type":29,"marks":692},"代理设置帮助",[693],{"href":694,"type":61},"https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings",{"text":63,"type":29},{"source":6,"id":697,"documentId":698,"translationKey":698,"locale":9,"slug":699,"path":700,"_path":700,"title":701,"description":702,"excerpt":702,"image":703,"publishedAt":704,"updatedAt":705,"author":17,"tags":706,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":707,"bodyHtml":230},4548,"m5w5f52o4gq0p4hqfasgz4h8","long-proxy-task-interruption-avoid-duplicate-processing","\u002Fblog\u002Flong-proxy-task-interruption-avoid-duplicate-processing","长时间代理请求中断如何避免重复处理数据","通过代理运行的长任务中断后，未收到响应不代表目标端未处理。本文说明如何用业务主键或幂等键记录状态，并在恢复前核对目标端，避免重复写入或提交。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_d3b959f788.webp","2026-11-19T03:28:04.700Z","2026-11-19T03:28:04.674Z",[],[708,712,716,720,724,728,732,758,774,778,782,816,820,824,828,838,842,846,880,888,892,896,900,904,908,912,916,920,924,927,931,935,939,943,947,951,955,959],{"type":25,"children":709},[710],{"text":711,"type":29},"长任务通过代理 IP 运行时连接中断，重新执行可能造成重复写入、提交或计费。常见原因是恢复逻辑把\"未收到响应\"误当成\"目标端未执行\"。",{"type":25,"children":713},[714],{"text":715,"type":29},"要避免这一点，先别急着找断点，先回答\"这一条到底处理完没有\"。把每条数据的处理状态做成可查询的，恢复时按状态决定跳过、重试还是转人工。网络恢复只是继续跑的前提，不是数据完整的证明。",{"type":35,"level":36,"children":717},[718],{"text":719,"type":29},"请求中断后，哪些情况可能导致数据被重复处理",{"type":25,"children":721},[722],{"text":723,"type":29},"重复处理通常来自几种情况：请求已到达目标端但回执丢失，客户端将超时当成失败后再次发送；写入成功后、更新本地完成状态前进程崩溃，恢复时又把数据当成未处理；多个工作进程同时领取同一批数据；或者客户端与中间层分别触发重试。检查点只能说明任务跑到哪里，不能证明这一条是否已经落地。因此，应结合客户端发送记录、目标端查询和业务侧可对账标识判断；证据不足时，将状态标为“结果未知”，不要仅凭客户端日志认定成功或失败。",{"type":35,"level":36,"children":725},[726],{"text":727,"type":29},"如何选择业务 ID、幂等键或内容指纹作为去重键",{"type":25,"children":729},[730],{"text":731,"type":29},"去重键的作用，是让同一条逻辑数据在任何一次重放中都能被认出来。三种常见做法各有前提：",{"type":304,"format":305,"children":733},[734,742,750],{"type":308,"children":735},[736,740],{"text":737,"type":29,"marks":738},"业务主键",[739],{"type":314},{"text":741,"type":29},"：订单号、任务 ID、URL 加版本号。最可靠，前提是目标端也用同一个键。",{"type":308,"children":743},[744,748],{"text":745,"type":29,"marks":746},"客户端幂等键",[747],{"type":314},{"text":749,"type":29},"：每条逻辑数据生成一次，重试时复用同一个键，不按\"第几次尝试\"生成。按尝试生成等于没有幂等。",{"type":308,"children":751},[752,756],{"text":753,"type":29,"marks":754},"内容指纹",[755],{"type":314},{"text":757,"type":29},"：对请求体做哈希。适合没有业务主键的场景，但内容一变指纹就变，还存在碰撞可能，只能作辅助。",{"type":25,"children":759},[760,762,765,767,772],{"text":761,"type":29},"幂等键只有在目标端认识并按约定去重时才有效；客户端自己记录键，不会让目标端自动去重。HTTP 方法本身的幂等语义见 ",{"text":115,"type":29,"marks":763},[764],{"href":118,"type":61},{"text":766,"type":29},"；迟到请求与安全重试的设计可参考 ",{"text":768,"type":29,"marks":769},"AWS Builders’ Library：Making retries safe with idempotent APIs",[770],{"href":771,"type":61},"https:\u002F\u002Faws.amazon.com\u002Fbuilders-library\u002Fmaking-retries-safe-with-idempotent-APIs\u002F",{"text":773,"type":29},"。键的粒度也要与可能重复的操作层级一致：粒度太粗会把不同操作合并，太细又无法识别重放。",{"type":35,"level":36,"children":775},[776],{"text":777,"type":29},"用四种处理状态判断任务中断后能否安全重试",{"type":25,"children":779},[780],{"text":781,"type":29},"四个状态足够覆盖大多数长任务。",{"type":304,"format":305,"children":783},[784,792,800,808],{"type":308,"children":785},[786,790],{"text":787,"type":29,"marks":788},"待处理",[789],{"type":314},{"text":791,"type":29},"：尚未发出。",{"type":308,"children":793},[794,798],{"text":795,"type":29,"marks":796},"处理中",[797],{"type":314},{"text":799,"type":29},"：已发出，未收到确定结果。进程崩溃后，这个状态不能自动回到待处理。",{"type":308,"children":801},[802,806],{"text":803,"type":29,"marks":804},"已完成",[805],{"type":314},{"text":807,"type":29},"：收到明确成功，或目标端确认存在。",{"type":308,"children":809},[810,814],{"text":811,"type":29,"marks":812},"结果未知",[813],{"type":314},{"text":815,"type":29},"：处理中超时、连接中断、进程崩溃后无法确认。",{"type":25,"children":817},[818],{"text":819,"type":29},"关键规则只有一条：处理中和结果未知，都必须先核对目标端，再决定去向，不得直接重置为待处理。恢复时允许的动作也只有三种——跳过（已确认完成）、重试（确认未完成）、转人工（无法确认且重放有副作用风险）。",{"type":25,"children":821},[822],{"text":823,"type":29},"状态要写到能跨进程重启的位置，并且每次变化都写，而不是任务结束时批量落盘。批量落盘省下的那点开销，往往就是重复处理的来源。",{"type":35,"level":36,"children":825},[826],{"text":827,"type":29},"重试前如何核对目标端处理结果和代理会话",{"type":25,"children":829},[830,832,836],{"text":831,"type":29},"切换出口后核对业务状态，可参考",{"text":833,"type":29,"marks":834},"切换代理 IP 出口后如何确认请求与业务状态没有回归",[835],{"href":137,"type":61},{"text":837,"type":29},"。代理连接或出口会话变化会影响传输与目标上下文，但业务回执应按稳定业务 ID、请求 ID及原幂等键关联。连接失效后仍可通过服务端状态查询对账，不能根据代理会话是否存活判断回执归属。",{"type":35,"level":21,"children":839},[840],{"text":841,"type":29},"查询接口、列表回查、计数和业务日志各适合何时使用",{"type":25,"children":843},[844],{"text":845,"type":29},"可按接口能力选择以下核对方式：",{"type":304,"format":399,"children":847},[848,856,864,872],{"type":308,"children":849},[850,854],{"text":851,"type":29,"marks":852},"查询接口",[853],{"type":314},{"text":855,"type":29},"：按去重键查单条状态，适合恢复前逐条确认。",{"type":308,"children":857},[858,862],{"text":859,"type":29,"marks":860},"列表回查",[861],{"type":314},{"text":863,"type":29},"：按时间窗或分页拉取目标端记录，与本地清单比对，适合没有单条查询的接口。",{"type":308,"children":865},[866,870],{"text":867,"type":29,"marks":868},"计数对账",[869],{"type":314},{"text":871,"type":29},"：目标端总数对比本地已完成数，前提是统计范围、时间窗、软删除、分页与异步落库的口径一致。它只能提示\"可能有差异\"，不能直接推断漏项，也不能定位到哪一条。",{"type":308,"children":873},[874,878],{"text":875,"type":29,"marks":876},"业务日志",[877],{"type":314},{"text":879,"type":29},"：目标端或下游的操作日志，按时间和去重键匹配，通常作为兜底。",{"type":25,"children":881},[882,884,887],{"text":883,"type":29},"目标端写入可能有延迟，刚写完查不到时，应按接口约定等待后再查。查询本身也可能触发限流，批量核对要控制频率。限流后的暂停与恢复思路，可参考",{"text":84,"type":29,"marks":885},[886],{"href":87,"type":61},{"text":63,"type":29},{"type":35,"level":21,"children":889},[890],{"text":891,"type":29},"没有查询接口时，如何降低重复处理风险",{"type":25,"children":893},[894],{"text":895,"type":29},"此时只能降级处理。目标端明确支持并保证该键语义时，才按最小粒度重放、复用同一个键，同时把这条标成\"可能重复\"，任务结束后统一对账。目标端不支持时，客户端带键不会让它自动去重，应保持\"结果未知\"，转人工或等可核实的回执。即便目标端支持，这条路径也只能降低重复概率，不能证明不重复，记录里要写明这一点，不要承诺\"绝不重复\"。",{"type":35,"level":36,"children":897},[898],{"text":899,"type":29},"发现重复数据后，如何对账并处理差异",{"type":25,"children":901},[902],{"text":903,"type":29},"重复一旦发生，顺序是\"先定位、再收敛、最后记录\"，不要边跑边改。",{"type":25,"children":905},[906],{"text":907,"type":29},"定位靠对账表，至少记六项：去重键、本地状态、目标端状态、差异类型、处理动作、处理时间。对账频率按任务量定，日终一次通常够用；数据量大、单条影响大时，改成每批一次。",{"type":25,"children":909},[910],{"text":911,"type":29},"对账结果只有三种，处理方式不同：",{"type":98,"children":913},[914],{"text":915,"type":29},"| 差异类型 | 表现 | 处理方式 |\n| --- | --- | --- |\n| 漏处理候选 | 本地有、目标端暂未查到 | 先按接口一致性约定等待并查询权威状态；确认未执行，或服务端仍有覆盖本次意图的有效幂等契约后，才可补跑 |\n| 重复处理 | 目标端同一键多条 | 保留一条，其余按业务规则撤销或标记 |\n| 状态不一致 | 两边都有但字段不同 | 按业务权威数据源、事件时间和一致性规则裁决；确认目标端记录不是暂态或延迟状态后，再回写本地 |",{"type":25,"children":917},[918],{"text":919,"type":29},"收敛动作要区分能不能自动做：补跑和回写状态可以自动；撤销、删除、退款这类有外部影响的操作，一律转人工。不要写\"发现重复就自动删除\"的逻辑，删错一条的代价通常比多留一条高。",{"type":25,"children":921},[922],{"text":923,"type":29},"补救完成后，把这次的差异类型和处理方式记录下来。如果同一类差异反复出现，说明状态机或键的粒度有问题，要回去改设计，而不是每次都靠对账收尾。",{"type":35,"level":36,"children":925},[926],{"text":187,"type":29},{"type":35,"level":21,"children":928},[929],{"text":930,"type":29},"代理 IP 重连之后，幂等键应该存在哪里？",{"type":25,"children":932},[933],{"text":934,"type":29},"与业务数据同一事务写入。分开写会出现\"数据落了、键没落\"，恢复时仍认不出。",{"type":35,"level":21,"children":936},[937],{"text":938,"type":29},"任务重跑会覆盖上次结果吗？",{"type":25,"children":940},[941],{"text":942,"type":29},"不能只按覆盖式或追加式判断。先核对版本冲突、计费、通知等副作用及服务端幂等约定；只有确认重放安全后才重跑。追加写也可能由唯一约束去重，不能一概断言会翻倍。",{"type":35,"level":21,"children":944},[945],{"text":946,"type":29},"状态一直停在\"处理中\"，能当失败重跑吗？",{"type":25,"children":948},[949],{"text":950,"type":29},"不能。处理中与结果未知都要先核对目标端，直接重置为待处理就是重复来源。",{"type":35,"level":21,"children":952},[953],{"text":954,"type":29},"两个工作进程同时拿到同一批数据怎么办？",{"type":25,"children":956},[957],{"text":958,"type":29},"用原子抢占：待处理→处理中必须一步完成。否则两边都以为自己是第一个。",{"type":25,"children":960},[961,962,965],{"text":223,"type":29},{"text":225,"type":29,"marks":963},[964],{"href":228,"type":61},{"text":63,"type":29},[967],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":968,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":969,"bodyHtml":230},[],[970,973,976,979,982,985,988,995,998,1001,1012,1015,1018,1021,1024,1027,1034,1037,1040,1047,1050,1053,1056,1059,1062,1065,1068,1071,1074,1077,1080,1083,1086,1089,1092,1095,1098,1101,1104,1107],{"type":25,"children":971},[972],{"text":28,"type":29},{"type":25,"children":974},[975],{"text":33,"type":29},{"type":35,"level":36,"children":977},[978],{"text":39,"type":29},{"type":35,"level":21,"children":980},[981],{"text":43,"type":29},{"type":25,"children":983},[984],{"text":47,"type":29},{"type":35,"level":21,"children":986},[987],{"text":51,"type":29},{"type":25,"children":989},[990,991,994],{"text":55,"type":29},{"text":57,"type":29,"marks":992},[993],{"href":60,"type":61},{"text":63,"type":29},{"type":25,"children":996},[997],{"text":67,"type":29},{"type":35,"level":21,"children":999},[1000],{"text":71,"type":29},{"type":25,"children":1002},[1003,1004,1007,1008,1011],{"text":75,"type":29},{"text":77,"type":29,"marks":1005},[1006],{"href":80,"type":61},{"text":82,"type":29},{"text":84,"type":29,"marks":1009},[1010],{"href":87,"type":61},{"text":63,"type":29},{"type":25,"children":1013},[1014],{"text":92,"type":29},{"type":25,"children":1016},[1017],{"text":96,"type":29},{"type":98,"children":1019},[1020],{"text":101,"type":29},{"type":35,"level":36,"children":1022},[1023],{"text":105,"type":29},{"type":25,"children":1025},[1026],{"text":109,"type":29},{"type":25,"children":1028},[1029,1030,1033],{"text":113,"type":29},{"text":115,"type":29,"marks":1031},[1032],{"href":118,"type":61},{"text":120,"type":29},{"type":25,"children":1035},[1036],{"text":124,"type":29},{"type":25,"children":1038},[1039],{"text":128,"type":29},{"type":25,"children":1041},[1042,1043,1046],{"text":132,"type":29},{"text":134,"type":29,"marks":1044},[1045],{"href":137,"type":61},{"text":139,"type":29},{"type":35,"level":36,"children":1048},[1049],{"text":143,"type":29},{"type":25,"children":1051},[1052],{"text":147,"type":29},{"type":25,"children":1054},[1055],{"text":151,"type":29},{"type":35,"level":36,"children":1057},[1058],{"text":155,"type":29},{"type":25,"children":1060},[1061],{"text":159,"type":29},{"type":25,"children":1063},[1064],{"text":163,"type":29},{"type":25,"children":1066},[1067],{"text":167,"type":29},{"type":25,"children":1069},[1070],{"text":171,"type":29},{"type":35,"level":36,"children":1072},[1073],{"text":175,"type":29},{"type":25,"children":1075},[1076],{"text":179,"type":29},{"type":25,"children":1078},[1079],{"text":183,"type":29},{"type":35,"level":36,"children":1081},[1082],{"text":187,"type":29},{"type":35,"level":21,"children":1084},[1085],{"text":191,"type":29},{"type":25,"children":1087},[1088],{"text":195,"type":29},{"type":35,"level":21,"children":1090},[1091],{"text":199,"type":29},{"type":25,"children":1093},[1094],{"text":203,"type":29},{"type":35,"level":21,"children":1096},[1097],{"text":207,"type":29},{"type":25,"children":1099},[1100],{"text":211,"type":29},{"type":35,"level":21,"children":1102},[1103],{"text":215,"type":29},{"type":25,"children":1105},[1106],{"text":219,"type":29},{"type":25,"children":1108},[1109,1110,1113],{"text":223,"type":29},{"text":225,"type":29,"marks":1111},[1112],{"href":228,"type":61},{"text":63,"type":29},null,[],[]]