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

Create generic error handling mechanism #10735

Closed
Tracked by #10732
RadhaRajagopalan opened this issue Aug 2, 2023 · 3 comments
Closed
Tracked by #10732

Create generic error handling mechanism #10735

RadhaRajagopalan opened this issue Aug 2, 2023 · 3 comments
Assignees

Comments

@RadhaRajagopalan
Copy link

No description provided.

@RadhaRajagopalan RadhaRajagopalan moved this to 📈 Todo in Team Studio Aug 2, 2023
@mlqn mlqn self-assigned this Aug 7, 2023
@mlqn mlqn moved this from 📈 Todo to 👷 In Progress in Team Studio Aug 8, 2023
@mlqn mlqn changed the title Catch asynchronous errors using Axios interceptors & display toast notifications Create generic error handling Aug 17, 2023
@mlqn mlqn changed the title Create generic error handling Create generic error handling mechanism Aug 23, 2023
@mlqn mlqn moved this from 👷 In Progress to 🔎 Review in Team Studio Aug 25, 2023
@mlqn mlqn moved this from 🔎 Review to 🧪 Test in Team Studio Aug 29, 2023
@nkylstad
Copy link
Member

nkylstad commented Sep 5, 2023

This seems to be working as expected!
One concern I have is the actual error message referencing our Slack as point of contact if something goes wrong - I think we need to refer our users to our servicedesk if something goes wrong rather than directly to Slack. Will investigate exactly where we should point our users and report back 😄

@mlqn
Copy link
Contributor

mlqn commented Sep 5, 2023

I have also created an issue suggesting a possible solution, which would be to create a contact page listing all the ways to get in touch: #10898

@nkylstad
Copy link
Member

nkylstad commented Sep 6, 2023

That's a great idea. I suggest we look into that in the next sprint, I have not gotten any replies on who/what we should set as the contact point yet.
I think we can just remove the line about contacting us from the error message for now, and then add it when we have created a "Contact" page that we can link to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants