On Again Off Again
I go to "Record Hints" and then to "Review and Attach" when the page comes up I see absolutely nothing, just a completely blank page. If I move the mouse around the blank page it see something becasue the pointer turns into the finger as to click on something. This situation comes and goes. Meaning the past couple of days everything worked just fine and I could see everything and now this morning it is back to the blank screen again. This has been going on and off for the past several months. Why? I had a friend that trouble shoots for Microsoft look and said everything was fine on my end that software on your side is the issue. Some programing issue that your program and Microsoft are not cooperating with each other. Please HELP.
Answers
-
Here's an attempt at select-all/copy/paste (these are some of the red/error messages, there's others also, but the big one at the end flashes too fact to grab it):
Some cookies are misusing the recommended “SameSite“ attribute 10
Loading failed for the <script> with source “https://js-cdn.dynatrace.com/jstag/15c157a40ab/ruxitagent_A2NVfqru_10253221019152312.js”. LL76-DWJ:110:142
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://auth.split.io/api/v2/auth?users=cis.user.MMM3-BZ6D&users=A_296. (Reason: CORS request did not succeed). Status code: (null).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/A_296. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/splitChanges?since=-1. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/A_296. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/splitChanges?since=-1. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/A_296. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/A_296. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/splitChanges?since=-1. (Reason: CORS request did not succeed). Status code: (null).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/cis.user.MMM3-BZ6D. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/splitChanges?since=-1. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/splitChanges?since=-1. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sdk.split.io/api/mySegments/A_296. (Reason: CORS request did not succeed). Status code: (null).
2
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://auth.split.io/api/v2/auth?users=cis.user.MMM3-BZ6D&users=A_296. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://auth.split.io/api/v2/auth?users=cis.user.MMM3-BZ6D&users=A_296. (Reason: CORS request did not succeed). Status code: (null).
0 -
I'm not a web programmer, but what I get from those error messages is that some combination of your internet connection and your browser are causing the FS page to not load fully. The only part of that that you have any control over is your browser: is it up to date? There could be a timeout or similar setting that has been changed, causing older versions to act too impatient. Or, is your browser "helpfully" saving the results of connectivity glitches and thereby perpetuating the problem? You may need to give it a thwack upside the head, in the form of clearing your FS-related cache and cookies.
1 -
In addition to the browser itself, there can be plugins or extensions that could have these kinds of effects. Anti-malware software or a VPN could be a factor. To troubleshoot these possibilities, you could try a different browser, and temporarily disable any VPN or anti-malware software and see if it works differently.
2 -
Did ALL of that and it is still happening
0 -
Let us know the original browser (make and version) that caused the error and the subsequent browsers you tried later (inc version please) that gave the same errors. That will help narrow down possible causes.
0
