Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Inbox - Link to page results in error. Fix available?

Avatar

Level 1

Looks like in 5.6.1 the link to the payload item, even if it is a valid page, results in an error. Looks like some sort of 404 error.

Noticed a few other threads in this forum that elude to the same issue but, each one has no responses and trying to click into any of those threads is resulting in a 502 Bad Gateway Request. So I apologize for the same question being asked again but, anyone know if there is a hotfix available for this?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi, Nikhil,

I believe there is a hotfix available to fix this.

Please contact Customer Care or your account manager to request it. You can reference 'CQ-328' as the issue identifier.

As a possible workaround, you should be able to access the same content from Notifications: http://localhost:4502/notifications.html

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Hi, Nikhil,

I believe there is a hotfix available to fix this.

Please contact Customer Care or your account manager to request it. You can reference 'CQ-328' as the issue identifier.

As a possible workaround, you should be able to access the same content from Notifications: http://localhost:4502/notifications.html

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----