Summary
Custom connector builder not retrying Post request until success as expected
Question
Hi
I am creating a connector using Custom builder… Requirement is Post request and get the status and retry until its success and download the data.
I am using Backoff Strategy & Response filter to retry the Status API until status = success. But is not working as expected. Plz see the screen shot. am i creating this correctly
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
Join the conversation on Slack
["custom-connector-builder", "post-request", "retry-strategy", "backoff-strategy", "response-filter"]
Can you paste an example http response body pretty please?
What do you see happen? Is retry not happening?
If you’re making a POST request, are you sure that the API does not treat this as a new export request, and therefore your “readiness timer” resets? Is there perhaps a GET endpoint to check the status?
Difficult to tell you more without seeing the API docs
Logs say it’s backing off for 0 seconds instead of 40, that’s weird.
Can you set a constant value backoff of let’s say 1 minutes or 30 seconds instead of using exponential? Let’s see if that’s the culprit.
I have tried with 20 , 60 , 90 secs (constant) … still the same
Attached log… Thanks for your help
It looks like after backoff time airbyte is not retrying the request… its just printing it out the first request… This looks like a bug… Let me know more information required
I haven’t had the time to look deeper but that looks sus to me:
Backing off_send(..) for 0.0s.
Why is it 0 seconds? Should be longer 
that was my initial thought as well… as per UI builder i have set back off time off time as 50… You can also see in the log its sleeping for 50 secs
Is this could be a bug?
What if you try back off, but remove the response filter?
My hunch is — is the filter making it retry instantly?
We have improvements scheduled for the error handler feature soon
Thanks Natik… here is response from the API & Request to API
Back off strategy is to wait for 40 secs then retry the API. and when the status become success then exit
But when i tried this method in connection its is retying the API every 40 secs but all the time its returning the status is pending (looks to me its not calling the API in the retry) becaz the status is the same(attached the log)
reason i know of is while its waiting for retry i have tried the Request manually and i can see the status is success