Workbox notifications throw an error after migrating from Confluence Cloud

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Symptoms

When clicking on the Confluence workbox to see notifications, the popup window contains an error.

The following appears in the atlassian-confluence.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 ERROR [http-80-9] [atlassian.event.internal.EventPublisherImpl] invokeListeners There was an exception thrown trying to dispatch event 'com.atlassian.mywork.host.event.BeforeCountNewNotificationsEvent@2e958769' from the invoker 'com.atlassian.event.internal.SingleParameterMethodListenerInvoker@53349d99'. -- referer: http://localhost:8090/dashboard.action | url: /rest/mywork/latest/status/notification/count | userName: admin java.lang.RuntimeException: currentApplication Caused by: java.lang.NullPointerException: currentApplication at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204) at com.atlassian.applinks.core.auth.trusted.TrustedApplicationsRequestFactory.<init>(TrustedApplicationsRequestFactory.java:31) at com.atlassian.applinks.core.auth.trusted.TrustedAppsAuthenticationProviderPluginModule$1.getRequestFactory(TrustedAppsAuthenticationProviderPluginModule.java:80) at com.atlassian.applinks.core.auth.ApplicationLinkRequestFactoryFactoryImpl.createRequestFactory(ApplicationLinkRequestFactoryFactoryImpl.java:119) at com.atlassian.applinks.core.auth.ApplicationLinkRequestFactoryFactoryImpl.getApplicationLinkRequestFactory(ApplicationLinkRequestFactoryFactoryImpl.java:106) at com.atlassian.applinks.core.link.DefaultApplicationLink.createAuthenticatedRequestFactory(DefaultApplicationLink.java:118) at com.atlassian.mywork.host.service.AppLinkHelper.execute(AppLinkHelper.java:59) at com.atlassian.mywork.host.service.AppLinkHelper.execute(AppLinkHelper.java:42) at com.atlassian.mywork.host.service.ClientServiceImpl.verifyAuth(ClientServiceImpl.java:145) at com.atlassian.mywork.host.service.ClientServiceImpl.verifyAuth(ClientServiceImpl.java:111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) ... 235 more

Diagnosis

Recent migration from Confluence Cloud to Confluence Server (self-hosted).

Cause

Application links have become corrupted and need to be removed and recreated.

Solution

Workaround

Alternative Methods of Deleting Application Links in Confluence

Resolution

ℹ️ If there is no link to remove the application link, refer to the workaround above to remove them.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.