fix(teams): no immediate acks for ms teams webhook

[icecrasher321]

Description

No MS Teams immediate ack mechanism.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 28, 2025 4:20pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Jul 28, 2025 4:20pm

[greptile-apps]

Greptile Summary

This PR removes the special asynchronous processing mechanism for Microsoft Teams webhooks and consolidates all webhook processing through the standard synchronous pathway. Previously, Microsoft Teams webhooks had their own dedicated processMicrosoftTeamsWebhook function that would immediately return an acknowledgment response while executing the workflow asynchronously in the background. This change eliminates that special case and routes all providers (including Teams) through the existing processStandardWebhook function.

The key architectural change is that Microsoft Teams webhooks now execute synchronously like all other webhook providers, meaning the workflow must complete execution before the HTTP response is sent back to Teams. To maintain compatibility with Teams' expected response format, the Teams-specific response structure ({ type: 'message', text: 'Sim Studio' }) has been moved into the standard processor with a provider check.

This change aligns the webhook processing architecture by removing provider-specific execution paths and ensuring consistent error handling, logging, and execution guarantees across all webhook providers. The consolidation simplifies the codebase by eliminating the dual processing paths that existed for Teams versus other providers.

Confidence score: 3/5

• This change could potentially cause timeouts for long-running workflows since Teams webhooks now execute synchronously
• The removal of async processing may impact performance and user experience for Teams integrations
• The apps/sim/lib/webhooks/utils.ts file needs careful review to ensure the routing logic and response formatting work correctly

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}