This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forย 
Search instead forย 
Did you mean:ย 

Pipeline Status Notification

Go to solution
NAl
Contributor

โ€Ž01-06-2022 01:20 AM

Hi there,

I know that we can receive notifications for Pipelines that run on Scheduled Tasks for a number of statuses such as started, stopped, failed and completed.

How can we do the same for a pipeline that fails or stops whilst running on a Consumer Snap where the Message Count is -1?

0 Kudos
1 ACCEPTED SOLUTION

Go to solution
koryknick
Employee
Employee

โ€Ž01-06-2022 06:53 AM

@NAI - you can set up a scheduled task to run on an interval - however long you want your longest downtime. Then simply set the task so it doesnโ€™t run if an instance is already running. That way you get notified if the job stops for any reason and it will automatically restart on the next interval.

You may also want to look into Ultra Tasks (premium feature).

View solution in original post

0 Kudos
7 REPLIES 7

Go to solution
koryknick
Employee
Employee

โ€Ž01-10-2022 06:56 AM

Looking at the current documentation, this limitation still exists.

https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438009/Scheduled+Tasks

You could also set a timeout on your read from queue to have the pipeline gracefully stop on a pre-determined interval and let the scheduled task restart it.

0 Kudos

Go to solution
NAl
Contributor
In response to koryknick

โ€Ž01-10-2022 06:58 AM

Thanks Kory

0 Kudos

Go to solution
cstewart
Former Employee
In response to NAl

โ€Ž01-11-2022 02:08 AM

The logic behind the 3-month limitation comes from the fact that we do a quarterly release, and the nodes on which the pipelines run should be restarting at least that frequentlyโ€ฆ