WesselWizardThe documentation for the API callback says: "When the execution of a callback fails (e.g. the callback server is down or the response contains an error), we try to resend it for a maximum of 5 times" https://beta.doc.bunq.com/basics/callbacks#retry-mechanism
I notice Bunq does the retry mechanism even if my HTTPS endpoint returns a HTTP 200.
How does the retry mechanism determine if a callback is an error?
BastiaanMaster@wesselt#200522 Hi Wessel!
Is it maybe possible that your server doesn’t respond within 3 seconds?
Check also this topic, this looks like the same issue?
https://together.bunq.com/d/37454-request-content-for-notification-filter-url-callbacks/
WesselWizard@Bastiaan#200527 Thanks, the 3 second timeout explains it. I do several calls to the bunq api before I return. Bunq is very slow when retrieving transactions: just 200 transactions (1 call) takes 1,5 to 3 seconds. So there is no way to reliably finish within 3 seconds.
AWS lamba does not allow a function to continue after the http reply. Looks like there’s no easy way out.
BastiaanMaster@wesselt#200528 Maybe it’s possible to only save bunq’s callback data and process it with an other script?
WesselWizard@Bastiaan#200530 I guess AWS has support for queueing or a database, but that would really complicate things.
Why the 3 second limit?
