1
Trigger
Received a trigger to execute a Job: Manual Trigger (via platform or API request), Event, Schedule, Component
2
Details
Based on given configuration, we are preparing the Job and keep updating it’s status upon progress (check statuses).
3
Updates
We constantly monitor and update status of the Job and send Notifications.
4
Finish
We track all the details including logs, warnings, errors, results of the Job so you can find it all in a single place.
Features
Triggers
Events- set up your event to trigger a job using real-time Events.Schedule- set up your schedule to trigger a job using cron-like Schedule.API Trigger- trigger a job via an API request.Component- trigger a job via code with Component including extra payload or .
Manual Trigger- trigger Job execution via a platform.
Retry Mechanism
Sometimes your job can fail due to defined (or not) error handling, e.g. you have a task to fetch currencies from API endpoint and save it to the Database, but your currency API endpoint is not reachable. You canRetry this job manually in a platform or configure automated retry-mechanism.
Asynchronous Execution
Jobs are configured to perform tasks asynchronously, they are distributed and ensuring efficient and timely operations. Your Components are executed and running in background.Scheduled Delivery
Configure your Component trigger to execute a job up to 30 days in advance.Notifications
Users can subscribe to receive real-time updates on Job status changes, staying informed about their operational progress.
Configuration
Besides the common properties likename, category, description, you can configure these properties.
| Property | Required | Description |
|---|---|---|
Component | Yes | You can select Component that will be executed upon request. |
Component Version | No | You can select specific version of Component, default: LATEST. |
Trigger Account | No | Select account that will be bound to execution context of a job (e.g. accessible with api.currentUser() method), default: System. |
Input
Similar to Endpoints Inputs you can configure some predefined flags.| Property | Required | Description |
|---|---|---|
Skip Libs | No | Whether the compiler should ignore Component Libraries during compilation. |
excludeLibs
You can configure the names of specific Component Libraries that should not be compiled into execution.
This might be useful if you have libraries that are still work in progress or used sometimes, by default RevoEngine compiles all libraries into execution context.
If you have some libraries that are
Active but they cannot compile (e.g. syntax error) you will get Errors of compiler (it should not affect execution if this library is not used, but warnings will come to your logs). Ideally they should be excluded with this option.