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

PCH Excerpt Generator: "Error: undefined" notification #2472

Closed
danielabloch opened this issue May 9, 2024 · 1 comment
Closed

PCH Excerpt Generator: "Error: undefined" notification #2472

danielabloch opened this issue May 9, 2024 · 1 comment
Assignees
Milestone

Comments

@danielabloch
Copy link

Is your feature request related to a problem?

When users attempt to use the AI-powered excerpt generator, but do not have access to it, they see this message:
error-undefined

Related to the snackbar updates we want to make in the Tools tab of the PCH: #2424

Describe the solution you'd like

Repeat the same message we show in the Tools tab of the PCH to customers who do not yet have access to the AI features.
image

Describe alternatives you've considered

None, because we decided on and implemented this message for other AI powered features. With this request we ensure the same message shows for all features.

Additional context

@danielabloch danielabloch added this to the 3.16.0 milestone May 9, 2024
@danielabloch danielabloch changed the title Update error message on AI-powered excerpt generator PCH: update error message on AI-powered excerpt generator May 9, 2024
@acicovic acicovic modified the milestones: 3.16.0, 3.15.1 May 15, 2024
@danielabloch danielabloch self-assigned this Jun 12, 2024
@acicovic acicovic modified the milestones: 3.15.1, 3.16.0, 3.17.0 Jun 17, 2024
@acicovic acicovic changed the title PCH: update error message on AI-powered excerpt generator PCH Excerpt Generator: "Error: undefined" notification Aug 9, 2024
@acicovic
Copy link
Collaborator

acicovic commented Aug 9, 2024

We've only seen this happen once. It surfaced on the VIP platform under circumstances which aren't entirely clear to us currently. It could need some special debugging to possibly be reproduced.

Although we haven't worked directly on this specific issue, much of the code in that area has been revamped when we were working on #2601, #2579, and #2580.

As such, this edge case might already be solved and I'm closing this issue. If we stumble upon it again, we'll reopen!

@acicovic acicovic closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants