With cancelled API form forwards: "re-send" versus "re-queue" payload?

Hi all --

With the form forward API, we are dealing with a backlog of "form forward"
cancels, because the recieving end had problems for a while. We have more
then 3500 cancels. :slight_smile:

1-- Can you tell me any important facts about the difference between the
"re-send" button and the "re-queue" button? I can guess that "re-send"
somehow "does it now" and shows you its success, while re-queue sticks it
in a queue... but can you confirm and tell me any other significance?

2-- ha ha, I know that there are "macros" that you can install in your web
browser to automate the pressing of certain buttons repeatedly... any
thoughts on my finding such a package doing a macro that will press the
re-queue button many, many, many times? Rube Goldberg was a cool guy.

Any other thoughts as well. Note, we have other theoretical options to
consider, but I want to explore these...

Thanks!
Eric

Hi Eric,

  1. You are correct. The "re-send" button will immediately retry that record
    a single time. The "re-queue" button will put that record back in the queue
    and will retry it another 3 times, as though it had just been added to the
    "pending" queue. I think you probably want to use the re-queue button in
    this instance.
  2. This sounds very frustrating, sorry! We don't currently have a way of
    selecting multiple records to re-queue at once, and I don't have any
    suggestions for browser add-ons for you to use. However, if you think this
    is something that would be useful in the future, you can add it to our
    uservoice https://dimagi.uservoice.com/ forum.

Best,

Farid

··· On Thu, Apr 20, 2017 at 6:06 AM, Eric Stephan wrote:

Hi all --

With the form forward API, we are dealing with a backlog of "form forward"
cancels, because the recieving end had problems for a while. We have more
then 3500 cancels. :slight_smile:

1-- Can you tell me any important facts about the difference between the
"re-send" button and the "re-queue" button? I can guess that "re-send"
somehow "does it now" and shows you its success, while re-queue sticks it
in a queue... but can you confirm and tell me any other significance?

2-- ha ha, I know that there are "macros" that you can install in your web
browser to automate the pressing of certain buttons repeatedly... any
thoughts on my finding such a package doing a macro that will press the
re-queue button many, many, many times? Rube Goldberg was a cool guy.

Any other thoughts as well. Note, we have other theoretical options to
consider, but I want to explore these...

Thanks!
Eric

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

OK. Since pressing “re-queue” 3500 times is clearly not a reasonable
situation… And since I think we can agree that many commcare users will
face a situation where the receiving side has a technical problem for a
period of time… I’ve made a userVoice item for this:

Can you go vote for this?

Thanks
Eric