Confluence logs filled with the error "Failed to process edge index task"

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.


This KB treats an error displayed in the application log file – atlassian-confluence.log


This problem may affect all versions of Confluence.


The following error appears In the atlassian-confluence.log:

WARN [scheduler_Worker-1] [search.lucene.queue.JournalIndexTaskQueue] lambda$processEntriesInternal$1 Failed to process edge index task for entry 'JournalEntry{id=1929260, journalId=JournalIdentifier{journalName=edge_index}, creationDate=2016-08-08 14:28:17.0, type=ADD_DOCUMENT, message={"edgeId":"131415156","userKey":null,"targetId":131415156,"date":null,"typeKey":"page.create"}}'
	at com.atlassian.confluence.plugins.edgeindex.LuceneEdgeDocumentFactory.getDocument(


The cause is an NPE in the Journalentry table of Confluence that handles the Edge Index. We observed that, in a few cases, this was caused by Copy Page Tree plugin. Specifically when a page didn't have an assigned creator and last modifier, which is causing an indexing issue. It's important to note that, while not having this plugin installed, this problem can have other causes.


Please, follow our guide to rebuild content index from scratch to fix it.

While using the Copy Page tree plugin, make sure all the pages have an assigned creator/last modifier. However, this is only a process to not trigger this error anymore, the index is still corrupt so we need rebuild it.

It's also possible, while not recommended, to query the database and fix the entry manually.

Before proceeding with an update query in the database, please, create a backup. This method is not supported by Atlassian. If a problem appears after perfoming the query below, please, revert the changes and rebuild the content index from scratch as advised.

  1. Shutdown Confluence
  2. Observe the error message and search for the problematic row, in the aforementioned error, we're searching for the targetId:

    select entry_id, message from journalentry where message like '%"targetId":131415156%';
  3. With the resulting entry_id, change the query below with the correct data:

    update journalentry set message = '{"edgeId":"131415156","userKey":"8ac0a0bc7447f9d10175aee69b6f0021","targetId":291275568,"date":1616086314,"typeKey":"page.create"}}' where entry_id = <entry-id>;

    If the date is null, check the date format of your database and system. In common Linux and PostgreSQL database, the date is likely following the Unix Epoch time

  4. Commit the change and restart Confluence

Last modified on Mar 25, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.