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