Nintex Page Not showing in List

Nintex Workflow is one of common and most sought after 3rd party Workflow engine in SharePoint because of its intuitive interface to configure workflow and the wealth of activities available for non-technical person in the organization to quickly create a Workflow in SharePoint environment. I recently encountered an issue with Nintex Workflow which I think is unusual but I still want to discuss this because it may be useful to someone who might encounter this as there is no good information available in Nintex documentation or in their forum.  nintex connect

I have Nintex Workflow 2010 installed and had put together a simple workflow for document management and approval. This Workflow was published in a Library and was working fine. A week ago we created a SharePoint page and added the Library web part with a view created.

Today when we wanted to change the workflow a little bit to include different approval department I navigated to the page where we added the Library previously and try to open the Nintex Workflow Management Page, to my surprise the management page nor the Nintex Workflow Create page is not found, but the workflow is still starting as soon as the document is added because it is set to start automatically.  

 

After poking around for some time and digging deep in the page I found that the List web part that was added earlier had “Toolbar type” set as summary toolbar. This has caused the Nintex Workflow page to not to show up. This I think is a bug with Nintex because if we can see SharePoint Designer Workflow management page we should also be seeing 3^rd part workflow management pages. 

Changing to Full Tool bar

 

Management Page started appearing again.

This could happen in default List Page in SharePoint if for some reason you wanted to have summary tool bar and not full tool bar.

 Hope this helps someone.

<Update>

This issue is not a bug as I noted earlier as you can see from Nintex Support in the comments. Thanks Nintex Support for your clarification. It appears that this is an issue with custom ribbon buttons.

</Update>