Times


images/download/thumbnails/44944910/arrow_up-version-1-modificationdate-1582788994388-api-v2.png Introduction: You can find a description of this phase in section Phase 1 (Introduction).


images/download/thumbnails/44944910/image2020-3-17_15-38-42-version-1-modificationdate-1584412721741-api-v2.png

There are several ways to start time-driven profiles.



Unlike event-driven Input Agents, time-driven Input Agents cannot start multiple threads per profile at the same time. Read in data is therefore always processed sequentially.

Special Cases


  • Profiles that have time-driven Input Agents configured with simple times, can also be triggered by another profile. If a job of such a profile is already running and if it is additionally triggered by another profile, a parallel job starts if the triggering profile sends a synchronous Message or if the maximum processing time of the triggered profile is greater than the lifetime of the sent Message, or if the lifetime of the Message is set to 0. See option Max. execution/life time in the Response Route Message.

  • If a profile is triggered, parallel processing is possible.

Deactivating All Profile Cronjobs


If there is a file ./disable_cron (can be empty) in the installation directory, all cronjobs (only profiles!) will not be executed as long as this file is present.