[UPD: The issue was solved by itself after a few days - no clue what influenced that]
Hi
Is anybody knows what it can be related to?
I'm being redirected to Minified React error #310 every time I try to access specific column Field settings. The column which triggers it has a tag type if it matters. But other columns Field settings even with a tag type open correctly.
It's just a simple table manually filled without any outer connectors.
I've also noticed that instead of showing a list of currently selected values (when I want to add another one value in the cell) the glitched column does not have any values selected shown even if they are actually selected.
Example of what I mean in case of normal column - there is currently selected a 'Finished' value and it shows it above the list and the 'Finished' value can be also removed and other values can be added there.
So this one part (highlighted by a red arrow) is missing even if the column shows to have values.
The glitched column only accept adding values to the cell since there isn't any list of current values with crosses right next to each one.
UPD It's also seems that the issue is unstable - I've just got another column glitched the same way, but after the page refresh I was able to get to the Field settings of it. Though the initial column still have the same issue and don't want to be fixed by itself after a page reload.
Any help is appreciated!
[UPD: The issue was solved by itself after a few days - no clue what influenced that]
Hi @Mariia Bov
I understand that you are facing issues with the Field settings while using confluence databases.
To troubleshoot the issue further, I have raised a support ticket here https://getsupport.atlassian.com/browse/JST-1139473.
You will receive all the updates through the support ticket directly.
Best Regards,
Vishalakshi N
Hi @Mariia Bov ,
Does this happen only in one specific database or on all databases across the site/instance for that specific column type?
Also, can you try using a different browser or incognito mode to see if the problem occurs there as well?
I've personally never seen this error. I've tried testing this on one of my demo sites and the settings are opening fine for that entry type.
If it's site-wide, your best bet is to contact Atlassian Support, as they can check backend behavior.
Also, there are no reported incidents related to DBs or Confluence in general 👀
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have this same issue. and it started 2-3 days ago.
Using different browser (Edge / Chrome) doesn't fix issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys,
It definitelly could be some backend issue then, as it only affects specific columns in specific databases.
I'll try to ask someone from Atlassian if they can take a look at it and get back to you.
Apart from that, you could also reach out to Atlassian Support for assistance and deeper troubleshooting.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am running into a similar issue w/ the 310 React errors on multiple Confluence DB pages.
I've encountered it in the following browsers in 2 different Confluence spaces:
This happens intermittently across several different databases that I have been creating and updating, and usually occurs when I am trying to interact with the Tag data type column.
I noticed that the "allow tag creation" toggle is also missing for any and all of the databases that I have created with Tag data columns. This toggle was present a couple of days ago, but has since disappeared
I have asked other Confluence users to check and they are experiencing the same in the same enterprise managed browsers and they also do not see the "allow tag creation" toggle, though none have reported the 310 error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Kai Käpölä
Alex Beaudet
Could you please say if you still have this issue present?
Mine has disappeared and I want to know if it's gone for everyone who had the error and if it not be back again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.