Closed reaper closed 1 month ago
Found a path to reproduce: each time you add a block and save, journey.next_scheduled_at
is set as null.
Thanks for reporting! Definitely an issue with how we were evaluating when to change that value. We update all of the steps on save, but if no changes had been made to the schedule that field wouldn't get set which would then cause it to null out. This has been addressed in the latest build, please give it a go and let me know if you run into any additional issues! Thanks!
Hi,
I've encountered an issue with a journey scheduled to run daily using a specific user list. Despite the setup, the push notification campaign is never triggered.
To troubleshoot, I replicated the journey to send emails instead of push notifications, and it worked as expected. Additionally, running the campaign manually or sending a proof to a specific user works fine as well.
Could you please advise on how to resolve this issue with the push notifications in the scheduled campaign?
Thank you!