I appreciate it when it's a small firm, they should definitely concentrate on resolving the issue first before communicating any problems. I must say that it's a shame that this is another instance of a company not showing an outage when there has been one. I can access the site now (couldn't for hours) but none of my flows are working and i cant see the run history to see if they are failing or just not running.
now it seems to be slowly coming back online. Oh, and thanks for saying where your flow instance is based, I'm sure that'll was down for me (UK). Glad you're at least getting some traction. Vote up the original post if you can, and any of those below it that are showing they're also having the issue. PS I'm not keen on cross referencing this account with this twitter account, but I've also mentioned it on Twitter For example, it will look something like:Īlso, upvote those of us indicating that we're also experiencing this, and upvote the initial post, too. What might be useful, and be to say which 'subdomain' you're sent to after login to your account. I would encourage everyone that can to log a ticket there, too, so that they're made aware of this, if they're not already. I *have* raised this as an issue in the 365 Admin Centre, though, since it isn't showing up on their reported issues, and at least 3 of us are reporting issues here. I actually don't know the infrastructure, tbh. maybe one or more of their datacenters is having an issue either with a particular service, or communicating with others. This looks like it's probably a resource thing, then, at MS.
0 kommentar(er)
