"Exit: 0" Error On Fetch Remote Datasets Task

[aramo]

To be completed by the original poster:

CMS Version

3.1.4

Player Type

Windows Client

Player Version

R305

Issue

Hello! We are trying to make use of remote datasets that refresh every hour. However, after a time, the fetch remote datasets task deactivates itself and a bug icon appears. Hovering over this icon gives an “Exit: 0” error. This prevents the datasets from updating at all.

I’ve tried to reactivate the task and rerun it, but at some point, it will stop again, and return the exit: 0 error. I also can’t seem to find anything related to this in the logs.

I’ve seen this error come up in the forum before:

Fetch Remote Datasets task Exit: 0

To be completed by the original poster: CMS Version 3.0.2 Player Type Windows Player Version windows 3 R301.1-301 Issue Fetch Remote Datasets task is not completing. The task displays a bug icon with “Exit: 0” displayed on a mouseover. All remote datasets are in an active layout. I do not get any notifications or entries in the error log indicating any reason why this task is failing. I have my log level set to debug. When I re-enabled the task to run manually, I got the same exit cod…

But it doesn’t seem like a resolution was found here. I’m not 100% sure how I would go about troubleshooting this. Any help is appreciated!

Thanks!

[pitoco02]

Hi, are you using Dokcer or Custom Install?

Make sure your Cacerts are up to date. I think it’s a good starting point

[aramo]

Hello! Currently, we are using Docker for our CMS.

[aramo]

Just following up on this. Any ideas as to why this might be happening?

[pitoco02]

Try to see in your database, in the “task” table, which value is in the “lastRunMessage” column referring to this task

SELECT `name`, `lastRunMessage` FROM task where name = 'Fetch Remote DataSets';

Maybe it’s reporting the reason for the bug

Send here the result

[aramo]

Solution was found! Turns out that the limit policy for the dataset needed to be set to “First In First Out”. It was previously set to “Stop Syncing”.

Thanks for your help @pitoco02 !