Hi @nbg62 - so you got 2 separate questions:1. `aio app run`, logs available from the asset compute worker, not available from the simple headless action. This is expected; because the asset compute worker (action) is invoked in a "non-blocking" mode, its activation record and logs are always saved ...

Hi @nbg62 - the URL of your action should be http://localhost:3233/api/v1/web/guest/HeadlessApp-0.0.1/barcode/.

@uuniyal - are you calling the JIRA REST APIs that's available within an intranet, e.g. corporate network? This is not possible because your Runtime action is not in the same intranet.So the called APIs must be publicly available over the internet.

@karan_sharma_di - do you have the issue with Adobe I/O Runtime specifically (running serverless action)?From the description it sounds like a question for the API Gateway?

@hegarg - For now, Adobe I/O Runtime only supports Node.js.Please refer to this page for all the supported runtimes currently.

ok, in that case you could still use the Files SDK to receive the file from the UI. When the Runtime action calls Workfront API, instead of simply giving the file URL, you would stream the file to the post request to upload in the "multipart/form-data" way. Here is a sample code from quick Google se...

Does the workfront API accept a URL to the file? I don't think using the Runtime action as a middleware to upload file is ideal because it makes the performance much worse, and the serverless action itself is not intended to handle files. Instead, the recommendation is to upload the files to Firefly...

What kind of API endpoints do you configure? Something you add manually, like a 3rd party system? Do you have different endpoints for prod, stage, etc. like prod.ext-service.net, stage.ext-service.net? And they change per workspace deployment?

@shelly-goel - a Firefly app is deployed to a workspace that you specify, which assigns a Runtime namespace and relevant State lib access for it.Speaking about app state, there are 2 separate concepts:build variables: used for building and deploying the app. Those are the values set in .env such as ...

@shelly-goel - the CORS policy is set by the server (workfront in this case), and you can not bypass it by changing your UI code.The recommended route would be: write a Runtime action to call the workfront API, processes the data, and returns it to the UI for rendering.