EnterpriseCrmFrontendsEventbusProtoTaskConfig
import type { EnterpriseCrmFrontendsEventbusProtoTaskConfig } from "https://googleapis.deno.dev/v1/integrations:v1.ts";
The task configuration details. This is not the implementation of Task. There might be multiple TaskConfigs for the same Task.
§Properties
Alert configurations on error rate, warning rate, number of runs, durations, etc.
User-provided description intended to give more business context about the task.
If this config contains a TypedTask, allow validation to succeed if an input is read from the output of another TypedTask whose output type is declared as a superclass of the requested input type. For instance, if the previous task declares an output of type Message, any task with this flag enabled will pass validation when attempting to read any proto Message type from the resultant Event parameter.
Optional Error catcher id of the error catch flow which will be executed when execution error happens in the task
Optional. Determines the number of times the task will be retried on failure and with what retry strategy. This is applicable for asynchronous calls to Eventbus alone (Post To Queue, Schedule etc.).
If set, overrides the option configured in the Task implementation class.
The set of tasks that are next in line to be executed as per the execution
graph defined for the parent event, specified by event_config_id
. Each of
these next tasks are executed only if the condition associated with them
evaluates to true.
The policy dictating the execution of the next set of tasks for the current task.
The customized parameters the user can pass to this task.
Optional. Informs the front-end application where to draw this task config on the UI.
Optional. Standard filter expression evaluated before execution. Independent of other conditions and tasks. Can be used to enable rollout. e.g. "rollout(5)" will only allow 5% of incoming traffic to task.
Optional. User-provided label that is attached to precondition in the UI.
Optional. Contains information about what needs to be done upon failure (either a permanent error or after it has been retried too many times).
Determines what action to take upon successful task completion.
Optional. Determines the number of times the task will be retried on failure and with what retry strategy. This is applicable for synchronous calls to Eventbus alone (Post).
Copy of the task entity that this task config is an instance of.
The policy dictating the execution strategy of this task.
REQUIRED: the identifier of this task within its parent event config,
specified by the client. This should be unique among all the tasks belong
to the same event config. We use this field as the identifier to find next
tasks (via field next_tasks.task_number
).