We’re trying something new and sending data directly to and AWS Lambda function with a lambda-url and an HTTP connection in Celigo.
This works great if there are no validation errors in the function.
If there’s an error thrown by the function, the celigo flow never stops running and retries the http call multiple times until it eventually gets a 403 from amazon.
Any ideas why this might be happening?
You're using AWS gateway on top of the Lambda function and using our HTTP connector to call it? What error code is returned when the function throws an error? Do you have auto retry enabled for your flow?
Hi Tyler,
I’m not the AWS guy at all. I’ll have to ask the developer at the client what they have done. I’m posting to a url that ends with .lambda-url.us-east-1.on.aws. I don’t think it’s a gateway on top of the function. I believe is just a setting within the function definition to allow it to be called directly via url.
I don’t see a retry setting on this flow. Only the auto resolve errors option.
I think the developer coded the error as a 500 which may be causing the retries. I’ll follow up with the developer.
Name is confusing, but auto resolve setting also does some auto retrying: https://docs.celigo.com/hc/en-us/articles/16182564553371-Retry-or-resolve-errors#h_01HB6MM6SCV78FG2G4JH9WQ8JC. If it's returning 500, I assume we are attempting to auto retry a few times because often times a 500 could be temporary.