Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page

Was this helpful?

Understanding Job Scheduling

PreviousUnderstanding how Impulse diffs contentNextMotation

Last updated 2 years ago

Was this helpful?

Impulse allows to scheduling Jobs, scheduling is the ability to use a cron expression to schedule when and how often to perform an action. This allows you to automatically perform these actions instead of having to manually press the button.

Also, Impulse support the pipe lining of Jobs, allowing you to run multiple jobs and run them either in parallel and/or after a previous set of jobs finished.

The following diagrams explain the impulse flow for scheduling a Job and the Impulse flow to Pipe lining one or multiple Jobs.

These diagrams use after the name of the service involved in each step the Rn format (example: Sync Manager (R1)) to denote the responsibility of the process in each step of the flow, the description of each service and responsibilities can be found under the section.

Services
Scheduling a Job flow
Pipe lining Jobs flow