Flow Updates | Constantly Denied Access Due to Updates

Hey @paul_n is there any way we can get around this happening all the time? It slows us down massively every day when we need to ask each merchant to go an visit Flow to push a silent update:

Could we just let collaborators with App access trigger these updates? They are silent updates anyway right? Or could they just be pushed without needing the merchant to take any action?

CC @kalen

The amount of times I need to write this message each day :pensive_face:

This isn’t controlled by Flow so might need a bit more info. Do you know how long merchants might not have opened Flow when you see that? After you have a merchant update the app, how quickly does it happen again?

It happened across all my clients a couple of days ago - before that it had been maybe a month or more. I’m guessing this is just when new flow app updates launch that require new app permissions.

1 Like

It’s hard to pinpoint as there are some merchants that I tried to access last week, and they had to update then. Then, this week, I had to ask them to visit again to update again.

And then, no matter how much I explain it, I always get the ‘I visited the link but nothing happened’ response :joy:

I just don’t fully understand the logic. I’m keen to understand why a user has to activate a silent update by visiting the app and why it can’t just roll out?

There aren’t any new permissions to grant or anything. Just a big bottleneck for us when working with so many merchants.

If you haven’t logged in for more than 30 days to an app, it’s expected that you’ll get that notice.

But you shouldn’t get it more frequently than that, or if you are accessing the app recently. We are asking around to see if there might be a defect.

1 Like