由于“下发统一消息接口”功能被收回吗无法使用，只能改成“公众号模板消息接口” 但“公众号模板消息接口”好像只有http请求方式，所以就得拿到access_token，我还得写一套保存access_token的代码来鉴权 感觉有点违背云开发的“免鉴权”模式，不知道官方有计划去实现吗？

    'https://api.weixin.qq.com/cgi-bin/token?grant_type=client_credential&appid=' + appId + '&secret=' + appSecrect 上面是调用公众号的接口，获取token。在小程序的云函数调用这个接口。 公众号已经把开发者本机IP地址加入到白名单。调试是通过的，能获取到token。 小程序云函数发布后，查看日志，发现有大量的错误，都是40164，但是IP的地址都是不同的， 我也不知道这些IP地址是来自哪里。[图片]

环境信息如下： appID:wx12319570d48a6d07 环境ID： cloud-jialian-7ggg5ihe90f73f3b 日志内容 Request ID: 9b91f094-b012-4f94-980e-4c6ef18bb3ff 上次你说是事务锁的问题， 但是现在问题是：就我一个人测试。 (node:8) UnhandledPromiseRejectionWarning: Error: collection.add:fail -501001 resource system error. [ResourceUnavailable.TransactionBusy] Transaction is busy. Please check your request, but if the problem persists, contact us.     at Object.toSDKError (/var/user/node_modules/wx-server-sdk/index.js:8089:19)     at Object.checkError (/var/user/node_modules/wx-server-sdk/index.js:1422:23)     at /var/user/node_modules/wx-server-sdk/index.js:1210:33     at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:8) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:8) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. t_notify add 返回结果 resp ：  {   "_id": "17e3426e622468561217cbd627c3cfaf",   "errMsg": "collection.add:ok" } t_notify add 返回结果 resp ：  {   "_id": "17e3426e622468561217cbd3625577cb",   "errMsg": "collection.add:ok" } (node:8) UnhandledPromiseRejectionWarning: Error: collection.add:fail -501001 resource system error. [ResourceUnavailable.TransactionBusy] Transaction is busy. Please check your request, but if the problem persists, contact us.     at Object.toSDKError (/var/user/node_modules/wx-server-sdk/index.js:8089:19)     at Object.checkError (/var/user/node_modules/wx-server-sdk/index.js:1422:23)     at /var/user/node_modules/wx-server-sdk/index.js:1210:33     at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:8) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) REPORT RequestId:9b91f094-b012-4f94-980e-4c6ef18bb3ff Duration:373ms Memory:256MB MemUsage:25.184959MB END

(node:11) UnhandledPromiseRejectionWarning: Error: collection.add:fail -501001 resource system error. [ResourceUnavailable.TransactionBusy] Transaction is busy. Please check your request, but if the problem persists, contact us. at Object.toSDKError (/var/user/node_modules/wx-server-sdk/index.js:8089:19) at Object.checkError (/var/user/node_modules/wx-server-sdk/index.js:1422:23) at /var/user/node_modules/wx-server-sdk/index.js:1210:33 at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:11) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:11) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. REPORT RequestId:8f02c1a7-ba87-4212-81fb-83ec4b9bab46 Duration:330ms Memory:256MB MemUsage:23.812546MB

在云函数中新增了事务，但是会经常出下面这个错误，请问这个地方的事物有什么限制么？ {"errCode":-501001,"errMsg":"collection.add:fail -501001 resource system error. [ResourceUnavailable.TransactionBusy] Transaction is busy. Please check your request, but if the problem persists, contact us."}

"errCode":43101,"errMsg":"openapi.subscribeMessage.send:fail user refuse to accept the msg hint: [FBdZ1a08444924]"，我现在微信设置已经允许接收消息了，但调用云函数发送消息的时候，就提示用户拒接接收