Skip to content

WA Group Message Triggers Failed to send #102

@akanshaaa19

Description

@akanshaaa19

Summary

GitHub Issue: WA Group Message Trigger Failure

Problem Statement: Scheduled WhatsApp group message for 6th June did not send.

Expected: The user expected the message scheduled for the "Bengaluru Stories 2026" flow on 6th June to be sent to the "Adda Bengaluru" WhatsApp group.

Actual Outcome: The message was not received in the group at the scheduled time (12 PM), despite the system showing that it was triggered.

Error Messages: No specific error messages were provided; the user noted all groups in the collection received the message except for the "Bengaluru Solve Squad" group.

Reproduction Steps:

  1. Schedule a WhatsApp group message for a specific date.
  2. Ensure correct trigger settings for the scheduled date in Quick Tools → Triggers.
  3. Monitor the scheduled send at the specified time.
  4. Confirm the group should receive the message, as reflected in Glific.

Additional Information: User provided a screenshot of the trigger configuration but did not share details about Maytapi connection status on 6th June. Further investigation may be required to determine if disconnection issues or flow structure limitations affected group sends.

Source

Original message

Hi <@1132952719586492478>

I had scheduled WhatsApp group messages for a collection on 5th and 6th June. The message for 5th June was sent correctly, but the message scheduled for 6th June was not sent.

Could you please check and let me know what the issue was?

Collection Name: Adda Bengaluru
Flow Name: Bengaluru Stories 2026

Full thread transcript

poonthamizhreapbenefit_41345: Hi <@1132952719586492478>

I had scheduled WhatsApp group messages for a collection on 5th and 6th June. The message for 5th June was sent correctly, but the message scheduled for 6th June was not sent.

Could you please check and let me know what the issue was?

Collection Name: Adda Bengaluru
Flow Name: Bengaluru Stories 2026

Glific AI doc bot (bot): Hi there! Thanks for flagging this.

I do not have sufficient info to answer this question. <@&1383715800632004648>, can you please chime in here?

Meanwhile, a few quick checks that usually explain why a single day’s group schedule is missed:

  • Trigger settings: In Quick Tools → Triggers, open the schedule you created for 6 June and confirm “WhatsApp Groups” is selected, the “Adda Bengaluru” collection is chosen, and the date/time window actually covered 6 June; this is the recommended setup for scheduling to group collections . Docs: WhatsApp Groups Automation Features
  • Flow structure: For group schedules, only a flow with a single Send Message/Media node is supported; multiple messages or waits will not run (only the first send is considered) .
  • Maytapi connection: Please confirm the Maytapi-linked phone stayed connected on 6 June; if it disconnected, sends to groups/collections will fail until it’s reconnected . Docs: WhatsApp Groups Automation Features

If everything above looks good, could you share a screenshot of the Trigger config for 6 June for “Bengaluru Stories 2026”? That will help us pinpoint what blocked the send.

Glific AI doc bot (bot): Was this helpful in resolving your query? Or do you need further support?

fawas003: <@1359439042349109338>
When I checked, all the groups in the collection had received the message except the "Bengaluru Solve Squad" group on 6th June. could you please confirm if that's the case?

poonthamizhreapbenefit_41345: Hi <@1384094705993777212>, Its showing as such in the glific. But in the groups we actually didn't received any message at 12PM.

Please check the screenshot attached

fawas003: <@1118428955859505224>
The message has been triggered to the group, but it was not received. Could you please take a look into this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    To Do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions