Can you "retry" callbacks when no status 200 is returned?

  • Idea
  • Updated 3 years ago
  • Implemented
Now, if a callback for a user update fails, it is never retired. Maybe you can retry after 5 minutes, after 1 hour and after a day to ensure the website using Spreedly gets the callback notification?
Photo of Maarten Balliauw

Maarten Balliauw

  • 3 Posts
  • 0 Likes
  • happy

Posted 3 years ago

  • 1
Photo of Duff OMelia

Duff OMelia, Official Rep

  • 282 Posts
  • 16 Likes
Do you mean this callback?

https://spreedly.com/manual/integrati...

If so, we do retry if we don't get the right response for that call.
Photo of Maarten Balliauw

Maarten Balliauw

  • 3 Posts
  • 0 Likes
Yup that's the one. Maybe you should mention you do retry as it's not clear from the UI. Anyways: thanks for the fast reply!
Photo of Duff OMelia

Duff OMelia, Official Rep

  • 282 Posts
  • 16 Likes
Gotcha. I just wanted to confirm I understand. When you say the UI, do you mean the docs for that callback? ( https://spreedly.com/manual/integrati... )

Or another page? It looks like the docs mention the retrying, but perhaps it could be stated more clearly? Thanks!
Photo of Maarten Balliauw

Maarten Balliauw

  • 3 Posts
  • 0 Likes
I'd say the docs and perhaps a small addition to the /details/edit URL for a site (eg Spreedly will POST a comma separated list of subscriber ids to this url whenever subscribers change. --> Spreedly will POST a comma separated list of subscriber ids to this url whenever subscribers change. It will retry X times if this URL can not be reached. )
Photo of Duff OMelia

Duff OMelia, Official Rep

  • 282 Posts
  • 16 Likes
Coolo! Thanks for the suggestions!