Sebastian Wiszowaty
Sebastian Wiszowaty
@v-muuppugund Anything between 8-16 CEST works for me. In addition we've also attempted to purge said ETM watchlist to no avail: ```pwsh # Purge parameters $table = "Watchlist" $column =...
@v-muuppugund Before closing this issue it was discussed on the call to provide a root cause, or an explaination on why this had happened. Otherwise this should not be closed
@v-muuppugund You would need to be running this for months to eventually hit that issue. A week is is nothing for this issue. It happens for pretty much every PB...
@bisskar But the issue here isn't that it takes 'some time to connect' or invoke. The issue here is that it just refuses to acknowledge that an incident had been...
@v-muuppugund What traces? What logs? I'm sorry but I don't think this is something I can get as I'm not a MSFT employee -> the issue isn't about the logic...
@v-muuppugund @v-sudkharat Not an acceptable solution, re-open. Again this is a big issue, it breaches the services' SLA.
@v-muuppugund Before closing the issue, provide a tracking Id.
@JonnyG365 - in my case the runs that **should've** occurred do not even show up in that, as if that trigger never fired :(. So it would seem that the...
@v-muuppugund - it would be hard to replicate because you need to have that particular type of incident and it be 'fresh', so not sure if that would be possible...