Actions in Project Firefly returning a 503 status code with some weird AWS Lambda error sporadically | Community
Skip to main content
R
rkishoreindraganti-1
April 15, 2021

Actions in Project Firefly returning a 503 status code with some weird AWS Lambda error sporadically

  • April 15, 2021
  • 1 reply
  • 5076 views

Hi,

 

I hope you are doing good!

 

We are facing a weird issue in our project firefly app development, in our API layer (using actions here; in node.js) we are trying to establish AEP datasets and issuing some query against the dataset using ODBC strategy (Not HTTP Query Service);

 

On invoking the REST endpoint that I stated above we are getting some weird error with a status code as 503 sporadically (Find the screenshot below).

 

 

 

This is being a show stopper to continue our development, we are feeling reluctant to proceed further considering this may be a limitation in the Adobe IO, your suggestions are much appreciated.

 

Please let us know the root cause and solution ASAP.

 

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

D
Adobe Employee
duynguyen_adobeAdobe Employee
Adobe Employee
April 15, 2021

Hi @rkishoreindraganti-1 - I assume you are calling your action via "https://your-namespace.adobeio-static.net/...", is that correct?

Please try replacing "adobeio-static.net" by "adobeioruntime.net", and try again.

The reason why you got this error is that, your action ran longer than 30 seconds and caused a timeout at the CDN "adobeio-static.net".

The "adobeioruntime.net" domain has a timeout of 1 minute, which is default for all web actions running on I/O Runtime.

That being said, a web request taking more than 30 seconds is considered very slow. Please re-visit the implementation to optimize it if possible, for example by moving the time consuming part to an async (non-blocking) execution.

As a side note, please also update your AIO CLI with "npm install -g @adobe/aio-cli". All the URLs should be on "adobeioruntime.net" in a recent CLI release.

K
kishoreindraganti
Level 2
April 15, 2021

@duynguyen_adobe : Thanks for the quick response, it is much appreciated! 

 

I have tried your approach on updating the @adobe/aio-cli though it is referring to adobe-io.static.net. Please find the below snippet. 

 

 

K
kishoreindraganti
Level 2
April 15, 2021

I am trying your other solutions, in the meantime, I just want to make things clear, it is not only on the CLI output, even the application also makes the call to adobeio-static.net only not to the adobeioruntime.net though I am using the latest CLI version.

 

 


"aio app run"  uses "adobeioruntime.net" but "aio app deploy" using "adobe-io.static.net"

Terms & ConditionsAccessibility statement

Loading footer...