Stopping an active Customer Journey affects users differently depending on where they are in the journey flow at the moment you stop it.
Here’s how it works:
- If a user has NOT yet reached a "Send Push" element: When you stop the journey, any users who are in a waiting state (e.g., within a "Time Delay" or "Wait for Trigger" element) will be stopped. They will not proceed further in the journey, and therefore, they will not receive any subsequent push notifications from that journey.
- If a user has already passed a "Send Push" element: Once a user passes a "Send Push" element, the notification is immediately sent from Pushwoosh to the platform's push gateway (Apple's APNs or Google's FCM). At this point, the message is considered "sent" from our side and cannot be recalled. Stopping the journey will have no effect on these messages.
- If the user's device was online, they would have received it instantly.
- If the user's device was offline, the platform gateway will hold the message and attempt to deliver it as soon as the device comes back online, provided the message's Time-To-Live (TTL) has not expired.
In summary: Stopping a Customer Journey only prevents users from receiving messages they haven't been scheduled to receive yet. It does not cancel the delivery of messages that have already been processed and sent to the platform gateways. This same logic applies to scheduled one-time messages.
Comments
0 comments
Please sign in to leave a comment.