Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

afterSave Webhook consumes event and afterSave trigger in cloud code does not run #9436

Open
apederse opened this issue Nov 15, 2024 · 1 comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@apederse
Copy link

apederse commented Nov 15, 2024

Issue Description

If afterSave on a class is handled both using cloud code AND afterSave webhook on the same class, then the webhook will consume the event and the afterSave trigger in the cloud code will not be triggered. Is this the expected behaviour or is it a bug?

In case there is a limitation that on the same class a trigger can only be implemented in cloud code OR webhook, then it would be very helpful if this would be explicitly mentioned in the documentation.

Steps to reproduce

Set up an afterSave cloud code "Parse.Cloud.afterSave(Parse.User....."
Set up an afterSave webhook on the _User class
Sign up a new user.

Actual Outcome

The webhook is triggered as expected but the afterSave cloud code is not triggered
(If the webhook is removed or disabled then the cloud code afterSave is correctly triggered)

Expected Outcome

afterSave Webhook AND cloudcode afterSave trigger would both run when a new user signs up.

Environment

Server

  • Parse Server version: 5.2.3
  • Operating system: Linux
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 3.0
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local
Copy link

Thanks for opening this issue!

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants