Slowness in loading assets metadata schema when Workfront connector is active | Community
Skip to main content
R
RahulMohan
New Participant
June 7, 2022

Slowness in loading assets metadata schema when Workfront connector is active

  • June 7, 2022
  • 3 replies
  • 2268 views

Hi Team,

Metadata schema in Assets is taking 3-5 minutes to load. For example, if I want to make any change in the metadata schema, I need to wait for 3-4 minutes for the schema to load completely. And this happens only when the Workfront connector configuration is active. Does anyone facing this sort of issue? If yes, please let me know how you have resolved it.

Thanks,
Rahul

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

D
digarg17
Employee
June 23, 2022

@rahulmohan  : WF Connector latest version 1.9.0 has been released and is more performant. You may want to upgrade and see if that helps.

    D
    digarg17
    Employee
    June 14, 2022

    Hi , which workfront connector you are using ? AMS or cloud assets ? Loading fine for us - using 2.0.1 connector.

     

     

      R
      RahulMohanAuthor
      New Participant
      June 14, 2022

      Hi,

      We are using 1.8.0 with cloud assets.

      Thanks,
      Rahul

        D
        digarg17
        Employee
        June 14, 2022

        You may want to check logs & reach out to the connector team. They might want you to upgrade to - the latest connector is 2.0.3 from ensemble although Adobe recommends to go with Enhanced workfront connector now which was released in Dec'21.

          manpreetk908
          manpreetk908
          New Participant
          June 7, 2022

          Hey @rahulmohan,

           

          Is there any error or query in the log that could be consuming time especially related to the work front?

           

          Regards,

          Manpreet

            R
            RahulMohanAuthor
            New Participant
            June 14, 2022

            Hi Manpreet,

            Not really getting any useful clue from the logs. However we have raised an adobe support ticket and they are trying to find the cause.

            Thanks,
            Rahul

              Terms & ConditionsAccessibility statement

              Loading footer...