Not sure… logger for tags.management.provider on TRACE might log the paths of every write happening if they’re for tags on a local provider. Could help.
I marked this as a solution. It does log every write that is happening, that’s great, however, it doesn’t log failures, so to find the failure I just have to look at the write requests that went out 45 seconds (default timeout) prior to the fault message I get. This is kind of a dead end for me however, there’s so many write calls going out that it’s nearly impossible to find which one(s) is/are causing this issue.
Process the status return values from writeBlocking().
Thanks Phil, I was 100% overthinking this.
No worries. I was also dazed and confused until @Kevin.Herron slapped me in the face. /:
1 Like