Demoing or "testing" push journeys with short intervals and/or testing them multiple times on the same device unfortunately quickly leads to problems. A correctly built sequence of push messages then suddenly looks broken.

None of this relates to a live operation with several hours or days and weeks between them.

Why is that?

The policies and anti-spam measures of the Apple and Google platforms prevent multiple updates in short intervals.

The effect is amplified if the same device tests passes of the same certificate one after the other. At some point, no more pushes arrive there at all.

Result of testing with short intervals: Pushes come

• not,
• delayed;
• after another link click
• all at once as soon as the measure then no longer takes effect.

The exact limits are not public ("may vary"), which is understandable for an anti-spam measure.

So if you create a Pass Journey or messages and want to test them, you should try to do as much quality assurance as possible before the pushes are then tested on the devices.