Skip to main content
Archived

Expose tm_priority parameter when publishing to notification service.

Related products:FME Flow
  • May 25, 2016
  • 1 reply
  • 30 views
L
Forum|alt.badge.img

Let's say that I have hundreds of jobs in the FME Server queue and that these jobs notify a specific topic (JOB_FAILED) on failure.

If I publish a workspace to the Notification service (subscribing to the JOB_FAILED topic), the triggered workspace will be placed in the queue at lowest priority letting me know that there is an issue only when all my jobs already queued are completed.

Currently, I can work around this by appending &tm_priority=10 to the target URL of the push subscription but I have to do this manually each time I publish the workspace.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

verdoodtdries
Enthusiast
Forum|alt.badge.img+23
  • verdoodtdriesEnthusiast
  • Enthusiast
  • February 23, 2017

larry,

This can be a solution for the issue you encounter.

https://knowledge.safe.com/questions/40368/can-you-assign-a-priority-when-publishing-a-worksp.html

Community Stats

32,749
Posts
124,194
Replies
41,251
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.