You can create an Ultra Task after you have created the Pipeline in SnapLogic Designer. You can create an Ultra Task in Designer or Manager. When you create an Ultra Task in Designer, the Pipeline is pre-selected when you open the Create Task dialog. When you create an Ultra Task in Manager, you must select a Pipeline to associate with the Task.
Creating an Ultra Task includes the following topics:
Name. Enter a name for the Ultra Task. This name is used in the URL when the Pipeline has unconnected inputs/outputs.
Unless otherwise noted, the names of any asset or project is limited to UTF-8 alphanumeric characters and these punctuation characters !"#$%&'()*+,-.:;<=>?@[\]^_`{|}~. |
Pipeline. Select the Pipeline to run from the Pipeline drop-down menu. This Pipeline is triggered when the Ultra Task is called. If applicable, edit any of the parameter values from the Pipeline.
Once activated, the associated Pipeline is started on the Snaplex using the Ultra run policy that is specified in the Task dialog window. The Ultra Pipeline consumes messages from the FeedMaster and processes input documents. The Pipeline restarts automatically after the Ultra Task or the Pipeline itself is modified and saved—including known child Pipelines and accounts that are not computed dynamically using an expression.
After you create and enable your Ultra Task, you can view details about the Task.
You can create email notifications based on the status of the Scheduled Task. If your Org supports Slack notifications, you can add Slack channels or recipients. To add recipients for Task notifications:
Recipients receive notifications based on the selections in the When Task has field.
You can configure the following settings for your Ultra Task. Each field has a default value, except where indicated.
You can specify how many instances of the Pipeline should be running on a Snaplex. For example, to achieve redundancy, you can configure an Ultra instance per document.
The default value is one instance per Snaplex.
If the Snaplex has five nodes and ten Ultra Task instances are actively running, then the Snaplex starts two instances on each node. The algorithm for distributing executions on nodes is based on how many Ultra Task Pipelines are running already. Each instance connects to the input queue, and receives notifications of message delivery as they come in.
When multiple instances are running, the message is delivered to a single instance. If the Pipeline or node fails for any reason, then the message is unacknowledged in the queue. Consequently, when the consumer is recognized as no longer being connected, the message returns to the queue and is picked up by another instance. In the correct configuration, messages should not be lost.
You can indicate the maximum number of consecutive failures in a short period of time by entering a value in the Max Failures field. When this threshold is reached, the Task is automatically disabled.
The default value is ten document processing failures.
Set this value to zero if the Task should never be disabled.
You can prevent an excessive number of documents from being queued on a single, slow execution. Once the execution reaches this threshold of documents being processed, requests are distributed to other instances of the Ultra Pipeline.
Set the Max In-Flight value to the maximum number of documents that can be processed by an instance at any one time.
The default value is 200 documents.
You can set this value to one, but doing so affects performance, because a value of one would disable the prefetching of documents. Set this value higher if the Ultra Task executions take a long time.
You can specify Pipeline parameters. If you choose a Pipeline that contains Pipeline parameters to run in the Ultra Task, then these Pipeline parameters also appear in the Create Task window, where you can modify them. In the following example, the parameter keys path, full, and table name are displayed, with their entries as the corresponding values.
In the full field, the values contain nested JSON.