Any changes to CommCare data forwarding API?

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST requests
from CommCareHQ instances right now. We’re investigating on our side, but I
wanted to ping you quickly to ask if there had been any changes to your
case or form forwarding service?

Best,
Taylor

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

··· On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote: > > Hey team Dimagi, > > At Open Function, we're getting thousands of unprocessable POST requests > from CommCareHQ instances right now. We're investigating on our side, but I > wanted to ping you quickly to ask if there had been any changes to your > case or form forwarding service? > > Best, > Taylor >

Hi Taylor,

We have made some changes to our Data Forwarding API over the past few
weeks. We aren’t aware of any issues currently, and we haven’t made any
changes to the code for 24 hours. Have you checked the Data Forwarding
report? That could provide some insight into whether or not it’s us or you.

Ben

··· On Wed, Jun 7, 2017 at 3:09 PM, Taylor Downs wrote:

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote:

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST requests
from CommCareHQ instances right now. We’re investigating on our side, but I
wanted to ping you quickly to ask if there had been any changes to your
case or form forwarding service?

Best,
Taylor


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Taylor,

If you think this is a regression on CommCare, do you think you could
submit a bug report with an example of why you think the request is
unprocessable?

As Ben said, we did make a bunch of changes recently, although they have
been running for a few weeks without issue.

If you do have access to the project space on HQ, you can see the repeat
record report that Ben mentioned by clicking the Gear Icon (top right) ->
Project Settings -> Data Forwarding Records. From there, if you select the
"Cancelled" state you should see which records failed 3 times, along with
the payload we sent, and the response we received from your server.

Let me know if you want any more info.

Cheers,

Farid

··· On Wed, Jun 7, 2017 at 3:13 PM, Ben Rudolph wrote:

Hi Taylor,

We have made some changes to our Data Forwarding API over the past few
weeks. We aren’t aware of any issues currently, and we haven’t made any
changes to the code for 24 hours. Have you checked the Data Forwarding
report? That could provide some insight into whether or not it’s us or you.

Ben

On Wed, Jun 7, 2017 at 3:09 PM, Taylor Downs downs.taylor@gmail.com wrote:

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote:

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST requests
from CommCareHQ instances right now. We’re investigating on our side, but I
wanted to ping you quickly to ask if there had been any changes to your
case or form forwarding service?

Best,
Taylor


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ben and Farid,

Thanks so much for your swift responses—I really appreciate it. We
identified the issue—a combination of a particular client setup and a
vulnerability in how we encode our data processing endpoint—which has now
been fixed on our end. The data forwarding report is quite helpful, and we
were able to reprocess messages by hand. Is there any way to re-send
messages in bulk?

Thanks again!

Taylor

··· On Thu, Jun 8, 2017 at 8:32 AM, Farid Rener wrote:

Hi Taylor,

If you think this is a regression on CommCare, do you think you could
submit a bug report with an example of why you think the request is
unprocessable?

As Ben said, we did make a bunch of changes recently, although they have
been running for a few weeks without issue.

If you do have access to the project space on HQ, you can see the repeat
record report that Ben mentioned by clicking the Gear Icon (top right) ->
Project Settings -> Data Forwarding Records. From there, if you select the
"Cancelled" state you should see which records failed 3 times, along with
the payload we sent, and the response we received from your server.

Let me know if you want any more info.

Cheers,

Farid

On Wed, Jun 7, 2017 at 3:13 PM, Ben Rudolph brudolph@dimagi.com wrote:

Hi Taylor,

We have made some changes to our Data Forwarding API over the past few
weeks. We aren’t aware of any issues currently, and we haven’t made any
changes to the code for 24 hours. Have you checked the Data Forwarding
report? That could provide some insight into whether or not it’s us or you.

Ben

On Wed, Jun 7, 2017 at 3:09 PM, Taylor Downs downs.taylor@gmail.com wrote:

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote:

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST
requests from CommCareHQ instances right now. We’re investigating on our
side, but I wanted to ping you quickly to ask if there had been any changes
to your case or form forwarding service?

Best,
Taylor


You received this message because you are subscribed to the Google
Groups “CommCare Developers” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to a topic in the
Google Groups “CommCare Developers” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/commcare-developers/Z49h7-Q_cRQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is there any way to re-send messages in bulk?

Currently no unfortunately, but that is something we’ve wanted to do for a
while. I wouldn’t be surprised if that becomes a feature sometime in the
future.

Ben

··· On Thu, Jun 8, 2017 at 1:56 PM, Taylor Downs wrote:

Ben and Farid,

Thanks so much for your swift responses—I really appreciate it. We
identified the issue—a combination of a particular client setup and a
vulnerability in how we encode our data processing endpoint—which has now
been fixed on our end. The data forwarding report is quite helpful, and we
were able to reprocess messages by hand. Is there any way to re-send
messages in bulk?

Thanks again!

Taylor

On Thu, Jun 8, 2017 at 8:32 AM, Farid Rener frener@dimagi.com wrote:

Hi Taylor,

If you think this is a regression on CommCare, do you think you could
submit a bug report with an example of why you think the request is
unprocessable?

As Ben said, we did make a bunch of changes recently, although they have
been running for a few weeks without issue.

If you do have access to the project space on HQ, you can see the repeat
record report that Ben mentioned by clicking the Gear Icon (top right) ->
Project Settings -> Data Forwarding Records. From there, if you select the
"Cancelled" state you should see which records failed 3 times, along with
the payload we sent, and the response we received from your server.

Let me know if you want any more info.

Cheers,

Farid

On Wed, Jun 7, 2017 at 3:13 PM, Ben Rudolph brudolph@dimagi.com wrote:

Hi Taylor,

We have made some changes to our Data Forwarding API over the past few
weeks. We aren’t aware of any issues currently, and we haven’t made any
changes to the code for 24 hours. Have you checked the Data Forwarding
report? That could provide some insight into whether or not it’s us or you.

Ben

On Wed, Jun 7, 2017 at 3:09 PM, Taylor Downs downs.taylor@gmail.com wrote:

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote:

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST
requests from CommCareHQ instances right now. We’re investigating on our
side, but I wanted to ping you quickly to ask if there had been any changes
to your case or form forwarding service?

Best,
Taylor


You received this message because you are subscribed to the Google
Groups “CommCare Developers” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google
Groups “CommCare Developers” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to a topic in the
Google Groups “CommCare Developers” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/commcare-developers/Z49h7-Q_cRQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wonderful. Thanks for all your help.

··· On Thu, 8 Jun 2017 at 13:59 Ben Rudolph wrote:

Is there any way to re-send messages in bulk?

Currently no unfortunately, but that is something we’ve wanted to do for a
while. I wouldn’t be surprised if that becomes a feature sometime in the
future.

Ben

On Thu, Jun 8, 2017 at 1:56 PM, Taylor Downs downs.taylor@gmail.com wrote:

Ben and Farid,

Thanks so much for your swift responses—I really appreciate it. We
identified the issue—a combination of a particular client setup and a
vulnerability in how we encode our data processing endpoint—which has now
been fixed on our end. The data forwarding report is quite helpful, and we
were able to reprocess messages by hand. Is there any way to re-send
messages in bulk?

Thanks again!

Taylor

On Thu, Jun 8, 2017 at 8:32 AM, Farid Rener frener@dimagi.com wrote:

Hi Taylor,

If you think this is a regression on CommCare, do you think you could
submit a bug report with an example of why you think the request is
unprocessable?

As Ben said, we did make a bunch of changes recently, although they have
been running for a few weeks without issue.

If you do have access to the project space on HQ, you can see the repeat
record report that Ben mentioned by clicking the Gear Icon (top right) ->
Project Settings -> Data Forwarding Records. From there, if you select the
"Cancelled" state you should see which records failed 3 times, along with
the payload we sent, and the response we received from your server.

Let me know if you want any more info.

Cheers,

Farid

On Wed, Jun 7, 2017 at 3:13 PM, Ben Rudolph brudolph@dimagi.com wrote:

Hi Taylor,

We have made some changes to our Data Forwarding API over the past few
weeks. We aren’t aware of any issues currently, and we haven’t made any
changes to the code for 24 hours. Have you checked the Data Forwarding
report? That could provide some insight into whether or not it’s us or you.

Ben

On Wed, Jun 7, 2017 at 3:09 PM, Taylor Downs downs.taylor@gmail.com wrote:

Just as an update, we think that we’ve narrowed this down to a single
CommCareHQ application, so less likely that there was a change on your side
but I’d still appreciate an “all clear” if there haven’t been any builds
that might affect the case or form forwarders today!

Taylor

On Wednesday, 7 June 2017 14:58:16 UTC-4, Taylor Downs wrote:

Hey team Dimagi,

At Open Function, we’re getting thousands of unprocessable POST
requests from CommCareHQ instances right now. We’re investigating on our
side, but I wanted to ping you quickly to ask if there had been any changes
to your case or form forwarding service?

Best,
Taylor


You received this message because you are subscribed to the Google
Groups “CommCare Developers” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google
Groups “CommCare Developers” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to a topic in the
Google Groups “CommCare Developers” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/commcare-developers/Z49h7-Q_cRQ/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to a topic in the
Google Groups “CommCare Developers” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/commcare-developers/Z49h7-Q_cRQ/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.