[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-10。"],[[["Private triggers allow you to divide large integration flows into smaller, manageable subflows that are only invokable by other integrations."],["Using private triggers can minimize costs, as they do not count towards execution run pricing, while also increasing security by restricting invocation to other integrations."],["Private triggers improve performance by reducing latency in sub-integration callouts, and their execution logs are visible within the invoker integration's logs."],["Private triggers must be tested in unpublished integrations, and they can be invoked from other integrations using specific flow control tasks such as 'Call Integration', 'For Each Loop', 'For Each Parallel', or 'While Loop'."],["Private triggers have a size limit of 25MB that they share with their parent integration, and the private workflow can not be called with a SYNC strategy if it includes async tasks such as 'Timer task', 'Suspend task' or 'Approval task'."]]],[]]