We’ve resolved the issue that was affecting Slack Triggers, where some output fields were not being returned as expected, leading to missing data errors in some Zaps.
An updated version of the Slack app caused the issue. We have rolled back to the previous version and migrated affected customers, which has restored full functionality.
Thank you for your patience while we worked to resolve this. If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.
No components marked as affected
Resolved
We’ve resolved the issue that was affecting Slack Triggers, where some output fields were not being returned as expected, leading to missing data errors in some Zaps.
An updated version of the Slack app caused the issue. We have rolled back to the previous version and migrated affected customers, which has restored full functionality.
Thank you for your patience while we worked to resolve this. If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.
Investigating
We are currently investigating an issue where Slack Triggers functionality is affected. Some output fields are not being returned as expected, resulting in missing data errors for some Zaps.
Our Engineering team is actively investigating this issue, and we will keep this status page updated as we learn more insights into the issue.
We really appreciate your patience while we work through this! If you require additional assistance, please feel free to reach out via our Support page: https://zapier.com/app/get-help.
