Scenario called repeatedly on its own when not specifically accessed

We are creating a WhatsApp integration for an onboarding flow.

The problem is that when I turn on the scenario for testing, something keeps hitting the scenario, sometimes a few times a minute. They error out, because they’re not ‘real’ calls from WhatsApp.

This has obviously burned through our monthly operation allotment VERY quickly.

What keeps calling our scenario?

Is there something on WhatsApp that constantly pings the scenario?

Welcome to the Make community!

1. Screenshots of scenario

Please share screenshots of scenario, modules, and error messages in question? It would really help other community members to see what you’re looking at.

You can upload images here using the Upload icon in the text editor:
Screenshot_2023-10-07_111039

2. Scenario blueprint

Please export the scenario blueprint file to allow others to view the mappings and settings. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.

Screenshot_2023-08-24_230826
(Note: Exporting your scenario will not include private information or keys to your connections)

Uploading it here will look like this:

blueprint.json (12.3 KB)

Following these steps will allow others to assist you here. Thanks!

2 Likes

Here’s the blueprint.

blueprint.json (1.2 MB)

Could you also click on one of those error scenario runs, click on the failing module’s output bubble, and take a screenshot of the error message?

2 Likes

Here’s the error. It isn’t receiving a “to” value, i.e. the phone number to send the message to. That should be available from the web hook, so this tells me that this isn’t coming from the right place. i.e. it’s not a real message from a user.

We are only testing, so there are only two of us who can message the WhatsApp app through Meta.

image

So, the big question is “what keeps calling this”?

It looks like your trigger module is a webhook. Where have you shared/copied this link into?

If you have shared with Whatsapp, they might be sending ALL events, so you might need to create a “filter” to only process the messages that have a valid number.


(This is just an example, change the mapping to an actual variable)

If you need further assistance, please provide the following:

Please provide the output bundles of the trigger module by going to the scenario History tab, then click the white speech bubble on the top-right of the module and select “Download input/output bundles”.
Screenshot_2023-10-06_141025

A.

Save each bundle contents in your text editor as a bundle.txt file, and upload it here into this discussion thread.

Uploading them here will look like this:

module-1-output-bundle.txt (12.3 KB)

B.

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles in this manner:

  • Either add three backticks ``` before and after the code, like this:

    ```
    input/output bundle content goes here
    ```

  • Or use the format code button in the editor:
    Screenshot_2023-10-02_191027

Providing the input/output bundles will allow others to replicate what is going on in the scenario even if they do not use the external service.

This will allow others to better assist you. Thanks!

2 Likes

Hi there. Here is the bundle from the webhook. It’s certainly incomplete, and definitely not a “real” message.

webhook-bundle-bad.txt (1.7 KB)

In contrast, here is the expected webhook result:

webhook-bundle-good.txt (1.6 KB)

I’ve been trying to create a filter after the entry point that will block an invalid request. However, the webhook still consumes an operation.

The main question is WHY the webhook keeps getting hit repeatedly in the first place. In the Meta WhatsApp webhook page, I am ONLY subscribing to messages.

I certainly can’t help with that because I don’t own WhatsApp, and as it appears to be a WhatsApp bug, you should report this to the Meta team.

Yes, but at least you save operations by not running the rest of the scenario.

Here’s a filter you can try

Screenshot_2024-04-19_230448

2 Likes