This article explains two errors that occur during journey execution. These errors can easily be prevented through attentiveness while creating a journey.

What you'll need:

Skill level: Easy

Time required: 3 minutes

The out-of-memory error

One journey execution is referred to as one transaction. Each transaction runs its own isolated container allocated with a finite amount of memory. 

When it can occur

The out-of-memory error occurs when the journey uses more memory than allocated. The error can be seen in the History section.

How to fix the problem

Generally, this issue is caused by one of the steps which are extracting a large quantity of data. It is advisable to fetch and process fewer records, in a batching mechanism so that memory utilization does not surpass the limit allocated.

The time-out error

Each transaction has a default 15-minute time span to complete the execution. If the transaction exceeds this execution time, the journey terminates with the time-out error. Please contact our team at support@quickwork.co to extend the transaction time span. 

When it can occur

The time-out error occurs when the journey is in the execution state for more than 15 minutes. The error can be seen in the History section.

How to fix the problem

Identify which steps are time-consuming, and try to optimize those processes. If you are sending data in a for loop, for instance, consider sending them in batches instead.  You can also move the common set of steps in a Callable Journey and then call it in the parent journey.