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