My Oracle Support Banner

MDS-00013 Error From MDS Mentions Taskflow that does not Exist in Application (Doc ID 2537792.1)

Last updated on APRIL 12, 2022

Applies to:

Oracle JDeveloper - Version and later
Information in this document applies to any platform.


On an ADF application, MDS error is seen while working with it in the standalone WLS server: MDS-00013 "no metadata found for metadata object" error from MDS

Error Log:
Caused by: oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/WEB-INF/<TASK-FLOW-DEFINITION>.xml"
        MDS-00201: PDocument not found in MetadataStore : [store-type=DefaultMetadataStore app-name=<APPLICATION> lookup-order=ServletContext,Classpath]
        at oracle.mds.core.MetadataObject.getBaseMO(
        at oracle.mds.core.MDSSession.getBaseMO(
        at oracle.mds.core.MDSSession.getMetadataObject(
        at oracle.mds.core.MOResolver.getMetadataObjects(
        at oracle.adfinternal.controller.metadata.provider.mds.MdsMetadataResourceProvider.getMetadataObjects(


Customer claimed the task flow object shown in the message included in the application code but still MDS complains about the file reference.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.