Workflow and Priority in the Queue | Community
Skip to main content
ivanp2522110
ivanp2522110
Level 2
June 15, 2016
Solved

Workflow and Priority in the Queue

  • June 15, 2016
  • 5 replies
  • 2266 views

Dear All,

I have a trouble with the Granite Workflow Queue. I have an automatic asset importer, which uploads a lot of assets. Each one creates a new workflow instance for DAM Update Asset. At some point the queue is really full and if in that time a human author uploads an asset, it takes up to 20 hours for the asset to be processed.

Is there any way to set a lower priority for some user, so that any new items go to the top of the queue and the rest is processed in the spare time?

Please point me in the right direction :)

Kind regards,

Ivan

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

Yes.. having different sling jobs is the only way in this scenario

5 replies

smacdonald2008
smacdonald2008
Level 10
June 15, 2016

I am checking with the WF ENG team for this, I am not aware of any flag or value that can be set. 

smacdonald2008
smacdonald2008
Level 10
June 15, 2016

Eng replied: 

"The only thing they could do today is figure out a way to have different workflows launched for these two conditions, and then configure different sling job queues for each workflow.  But if they are using workflow launchers in both cases it’s not possible today to start a different workflow per user, or based on how many workflows have been started etc."

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
June 16, 2016

Yes.. having different sling jobs is the only way in this scenario

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
June 16, 2016

Hi,

  • you didn't say which version of AEM you are using?
  • Are you regularly importing a lot of content, how much in a day?
  • After how many imports/size of import is the issue seen?

Rather than trying to implement a solution to work around the problem, you might consider how you are importing your content and see if you can use some logic, such as throttling [0], to slow down the ingestion of assets and therefore not affect the authors performing their tasks.

Regards,

Opkar

[0] https://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/scaling.html

ivanp2522110
ivanp2522110Author
Level 2
June 16, 2016

Thank you a lot, guys!

All very good ideas. I will try to do both: separate sling jobs and throttling.

For info, we are running 6.2 and normally there is not so much data, but every now and then there is a push of several GB in many separate image and video files.

Thank you again and be well!

Ivan

Terms & ConditionsAccessibility statement

Loading footer...