Search Crosser Knowledge Base

Delayed startup processing

Sometimes you need to do something once when the Flow starts. The Interval module can be used then, by setting the interval to 0 and making sure ‘Run on start’ is enabled. However, in certain situations you can’t initiate this action immediately when the Flow starts, because you have to wait for some other processing, like connecting to an external system or processing some code.

By combining the Interval and Delay modules you can create one-time triggers at any time after the Flow starts.

About the author

Goran Appelquist

Göran has 20 years experience in leading technology teams. He’s the lead architect of our end-to-end solution and is extremely focused in securing the lowest possible Total Cost of Ownership for our customers.

"Hidden Lifecycle (employee) cost can account for 5-10 times the purchase price of software. Our goal is to offer a solution that automates and removes most of the tasks that is costly over the lifecycle.

My career started in the academic world where I got a PhD in physics by researching large scale data acquisition systems for physics experiments, such as the LHC at CERN. After leaving academia I have been working in several tech startups in different management positions over the last 20 years.

In most of these positions I have stood with one foot in the R&D team and another in the product/business teams. My passion is learning new technologies, use it to develop innovative products and explain the solutions to end users, technical or non-technical."