Bug for intervals when started as "On Page/App Load" trigger with loader flag

Help & Support đŸ’» Bug Reports 🐞
1

I found a bug concerning the interval action step when used in combination with “On App/Page Load” triggers when the “Delay actions with loader” flag is enabled.

Setup:

  • Create 2 actions, A and B
  • Action A only has a interval step
  • Action B can be anything
  • Assign both either as “On Page Load” or “On App Load” triggers and enable the “Delay actions with loader” flag for the trigger with the interval action

Now every time the interval runs, it also starts action B, even though it is never explicitly called except for the “On App/Page Load” trigger. In fact, every other action assigned to one of those triggers will be executed when the interval runs.

Workaround: Have another action act as proxy for starting the interval. So basically create an action that starts the interval and assign that for the “On App/Page Load” trigger.

2

Hi Max,

We’ve confirmed this is a bug. As a workaround, please run the interval as a non-blocking load action by disabling “Delay actions with loader” for that trigger. Alternatively, create a proxy action that starts the interval, assign the proxy to On App/Page Load, and leave the loader flag disabled for the proxy. Other load actions can still use the loader normally.

I’ve escalated it to the dev team for investigation.

1 Like