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