Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
hi,
we created simple headless action and asset compute worker in the same project, logs are written using (for example)
Gelöst! Gehe zu Lösung.
Anhand von Themen werden Community-Inhalte kategorisiert und Sie können so relevanten Inhalt besser finden.
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 (for 7 days); on the other hand, the headless action is invoked in a "blocking" mode (web request), so its activation record is not saved (when the action runs successfully). For debugging purpose, you can enable the activation record to be saved by adding this header to the web request "x-ow-extra-logging: on". Please remember to remove this header in production, as it may impact your action performance. More details at: https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/gui....
2. The problem you are seeing is because you are calling your action on I/O Runtime (at https://80xx-xxheadlessapp-xxdemows.adobeioruntime.net/api/v1/web/xxHeadlessApp-0.0.1/myaction/), while in the command line you are getting activation records from localhost (by running `aio app run --local`). Please note when you run your app in localhost, the action URL should be like https://localhost:3233/api/v1/web/guest/xxHeadlessApp-0.0.1/myaction.
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 (for 7 days); on the other hand, the headless action is invoked in a "blocking" mode (web request), so its activation record is not saved (when the action runs successfully). For debugging purpose, you can enable the activation record to be saved by adding this header to the web request "x-ow-extra-logging: on". Please remember to remove this header in production, as it may impact your action performance. More details at: https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio-runtime/master/gui....
2. The problem you are seeing is because you are calling your action on I/O Runtime (at https://80xx-xxheadlessapp-xxdemows.adobeioruntime.net/api/v1/web/xxHeadlessApp-0.0.1/myaction/), while in the command line you are getting activation records from localhost (by running `aio app run --local`). Please note when you run your app in localhost, the action URL should be like https://localhost:3233/api/v1/web/guest/xxHeadlessApp-0.0.1/myaction.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten