Scheduled DataExchange Job Not Firing in DHIS2 Scheduler app

Support - Assistance technique
1

Hello everyone,
We are encountering an issue with a scheduled DataExchange Job in the DHIS2 Scheduler app. Although the job is scheduled correctly and no errors are reported in the response (errorReports: []), the job does not seem to fire the Process as expected.

When I manually trigger the job from the DX app it works perfectly. However, the scheduler does not run the process. When checking the /api/scheduling/running endpoint, it shows the status as “RUNNING,” but the process (DX Request) does not start.

Response from /api/scheduling/running
“AGGREGATE_DATA_EXCHANGE”: [
{
“jobId”: “DailyJobtes”,
“status”: “RUNNING”,
“description”: “Aggregate data exchange of 1 exchange(s) started”,
“startedTime”: “2024-09-17T03:57:58.964”,
“stages”: [
“exchange aggregate data 3q daily to INTERNAL target (local)”
]

I have tried both upgrading and downgrading the Scheduler and Data Exchange app versions, but the issue still persists. The issue remains consistent across the different versions.

Here are the details:

  1. DHIS2 Version: 2.40.4.1
  2. Scheduler Version: 101.6.9
  3. The internal Time Zone is Different (May be Conflicting with Scheduler Service, not sure)
  4. DX Exchange Payload is Single and not shared across different scheduled Job
    Has anyone else encountered a similar issue, or does anyone have suggestions on how to resolve this?
1 Like
2

Hi @arslan_mughal
I have a question please to clarify something please.

What is the expected the result that happens when manually triggering the job compared to when it says “running”. Does the scheduled job starts running at the scheduled time but doesn’t give the expected result?

Thanks!

3

Both the manually triggered and scheduled(Through Scheduler) DataExchange jobs show the same status and response. They appear as “Running” and “Completed” within a second, even though the ADX job should take more time to execute fully. In both cases, the job status shows as “Running” and “Completed,” but the ADX process is not actually being Fired.

4

Its think its a bug, I have same issue, you can create a JIRA ticket

5

The Problem is Solved, I was selecting DataElements instead of Program Indicator (Always Use Better Naming Conventions for Differentiation) :confused: :relieved: (Data Elements and Program Indicators Names were Same)

1 Like