Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False "Cannot read properties" error appears sometimes when saving a question #31766

Closed
cdeweyx opened this issue Jun 21, 2023 · 1 comment · Fixed by #34786
Closed

False "Cannot read properties" error appears sometimes when saving a question #31766

cdeweyx opened this issue Jun 21, 2023 · 1 comment · Fixed by #34786
Assignees
Labels
Difficulty:Hard .Frontend Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Type:Bug Product defects
Milestone

Comments

@cdeweyx
Copy link

cdeweyx commented Jun 21, 2023

Context

Not something that I can reproduce every time, but I am seeing this error fairly frequent (at least once a day) when I edit questions in a dashboard and try to save: Cannot read properties of undefined (reading 'id'). Despite the error, it does save as there is no error in the API call nor js console. Slack context.

Steps to Reproduce

If you duplicate the Self-Service Business dashboard into your personal collection, and then try to edit each card (changing the name or the sql), and save, you should be able to hit the problem with at least one of the cards. I click thru each card from the dashboard, click on question link if not showing the original question, make edits, then save, and click on the “Back to ” link next to question title to go back to the dashboard to repeat the process.

Image

@cdeweyx cdeweyx added .Team/42 🌌 Type:Bug Product defects labels Jun 21, 2023
@cdeweyx cdeweyx changed the title False "Cannot read properties" error when saving questions False "Cannot read properties" error appears sometimes when saving a question Jun 21, 2023
@deniskaber deniskaber self-assigned this Jun 21, 2023
@cbalusek cbalusek added Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness and removed Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness labels Aug 8, 2023
@paoliniluis paoliniluis added Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness .Frontend labels Oct 16, 2023
@paoliniluis
Copy link
Contributor

This is something that has started to happen more often in 47.3

This was referenced Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficulty:Hard .Frontend Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Type:Bug Product defects
Projects
None yet
5 participants