Oracle Cloud EPM Pipelines

Oracle Cloud EPM Pipelines – Batch Timeout in Minutes

Lydia Maksoud
Senior EPM Consultant

Recently I came across an issue with Oracle Cloud EPM Pipelines where if a job was taking longer than around 30 mins in a pipeline, the pipeline would move onto the next job without letting the job finish. The job would also show as “RUNNING” in the pipeline email notification and the email would say the pipeline has failed. Even when we check the job console, none of the jobs in the pipeline are shown as failed.

For example, the pipeline below moves on even though the aggregation is still running which then means the remaining jobs are not running in the correct order and the pipeline status shows as FAILED:

Oracle Cloud EPM Pipelines

After asking on Customer Connect, a helpful user (thank you Ija Vidaurri!) gave us the solution, which is to set the Batch Timeout in Minutes setting to a higher value (by default this is empty so I’m not sure of the exact default timeout!).

This can be done by going to Data Exchange -> System Settings and entering a minute value into the Batch Timeout in Minutes setting. In our case, we set it to 120 minutes, to ensure all jobs have enough time to finish before the pipeline moves on:

Oracle Cloud EPM Pipelines

Hopefully this will help if you’re experiencing a similar issue! Going forward I’d recommend always updating this setting when implementing Oracle Cloud EPM Pipelines, to avoid any potential problems with timeout.

For more on working with pipelines, see my previous blogs:

Until next time

Lydia