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