Actions
Bug #21418
closed
Campaign scheduler seems to not look for existing campaign at boot
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
It seems that is a campaign exists in repo, but the next event was not already generated, then rudder does not generate it when it starts.
It looks like when the scheduler is inited, it misses a foreach(campaign in enabled campaigns) { check if next scheduled event is correct or if none, generates it}
See PR with the failing test
Updated by 
Updated by 
Updated by Anonymous
Actions