Since your lemonflow-saas project has many services connected to the same repo, the services that are not triggering likely have watch paths configured that don't match the changed files, causing deployments to be skipped. You can verify this by checking each non-triggering service's Settings tab for its watch path patterns - note that patterns operate from / regardless of root directory setting, and any commit that doesn't match a service's watch paths will skip that service's deployment.

We're aware of an issue where GitHub pushes are not reliably triggering deployments for some services. Our team is actively investigating. As a workaround, you can manually trigger deployments using the Command Palette (CMD/Ctrl + K, then "Deploy Latest Commit"). We'll follow up once the issue is resolved.

Also facing the same issue

Thanks for letting us know. We are tracking the issue and you should be able to use the same workaround.