this._actionsCache is undefined

Hi I’m just wondering what this error message actually means?

image

I can’t seem to find anything in the sg console or the sg desktop logs that indicate where or why this error is being generated.

We’ve started getting it where we’re trying to run a distributed config alongside a centralised config.

Any help in troubleshooting this would be much appreciated :slight_smile:

Thanks in advance!

2 Likes

Interestingly I get a different error when using Google Chrome. (The above example was from Firefox).
image

We’re not getting the same error from one of our other shotgun accounts, and the one I’m trying it from does have some strict firewalls applied to it so I’m wondering if it could be related to that.

I’ll keep things posted here :slight_smile:

1 Like

Both errors seems to point to the same issue, with different wording. Both seems to complain about accessing something that is undefined where it should not.

2 Likes

I had a similar issue where I was actively doing things that corrupted the external command cache. My fix around that was to remove the cache completely. You might want to try to remove it (while keeping a backup of it so we can look at it) so you can know if it’s caused by a corrupted cache.

2 Likes

Thanks for you reply.

I had tried removing the entire Shotgun folder in %AppData% which I would presume would remove any caches or potentially corrupted files. However I still get the results seen above after having cleaned things out and started fresh…so I’m not sure that’s what’s causing this.

1 Like

Turns out I was mistaken about the firewalls issue, so it’s not going to be that…

It would be really good to know where this error is generated from, and what actually causes it so I can troubleshoot it more.

Thanks
Tom

Are you getting any errors in the chrome/firefox javascript console?
If you are please could you post them, feel free to send a support ticket in for that if you’d prefer not to post it publically.

Hey @philip.scadding Thanks for getting back :slight_smile:

Yeah, I didn’t think to check that (I never had to look for errors there before).

I am getting this error about authentication (from Chrome):
image

And I get this from Firefox:

I’ve tried signing in and out, and even deleted the entire Shotgun folder in %AppData% and I still get this result. Is there anywhere else that Sg might be storing authentication information other than in %AppData%?

Let me know if there’s anything you understand from this that we can troubleshoot. Unfortunately I’m not really able to fully understand how to troubleshoot these messages.

Thanks

Tom

Thanks
In the chrome output, I’m seeing You are not authorized to make browser.....
Are you logged in as the same user in both the browser and SG Desktop?

Looking at the code, I think it would be good to get a copy of your tk-desktop.log with debug enabled. Please could you pop a support ticket in with that?
I’m sorry your’ having issues with this!

… well this is embarrassing :flushed: :man_facepalming:. It would appear that turning the machine off and on again seems to have solved the issue!

I did also change my SG password to make sure that there were no “residual” credentials being stashed somewhere, so that might have been part of it too.

Either way it would appear that the issue has resolved itself!

@philip.scadding @geffrak thanks for your help!

2 Likes

Not at all, this is of interest. I’ve heard of similar issues before, they also have seemingly gone away as well, which has meant we’ve not got to the bottom of it. I’m not sure what triggers this.

1 Like

True I suppose. It is frustrating how many tech issues (in all area’s not just Shotgun!) can be solved with the “Have you tried turning it off and on again” approach!

I guess it’s just a very “Friday” problem :stuck_out_tongue:

2 Likes