You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently outbound push requests are processed one at a time but with the introduction of delaying sending requests immediately by using a cron in the outbound config then the ability to batch all requests that match the criteria into one request would be helpful.
Describe the solution you'd like
A way to have batched requests when using the outbound push feature
Describe alternatives you've considered
Using the feature as is and processing one request at a time
Hello Njuguna,
My request for implementing batch processing of records when Cron's conditions are met is backed by the need to adequately utilize the server capacity for the "Receivers" in this case DHIS2. This means that DHIS2 will have a single incoming payload with all the records compared to current setup which entails 1 payload per record. For instance if you have 200 records then you will see 200 payloads when cronjob's time is met instead of 1 payload with 200 data records.
Let me know if it makes sense.
Thanks,
Job
Is your feature request related to a problem? Please describe.
Currently outbound push requests are processed one at a time but with the introduction of delaying sending requests immediately by using a cron in the outbound config then the ability to batch all requests that match the criteria into one request would be helpful.
Describe the solution you'd like
A way to have batched requests when using the outbound push feature
Describe alternatives you've considered
Using the feature as is and processing one request at a time
Additional context
Forum post asking about this.
The text was updated successfully, but these errors were encountered: