I diged into the issue (I managed to enable debug logging for shared
validators used in the worker sequence) and my findings are:- Asset
compute service is called fine- Asset compute service calls my worker
and it fails with 403- The reason is that the
/adobeio/shared-validators-v1/headless used in my worker sequence throws
403 response code as for some reason my input IMS Org ID doesn't match
with the string literal "true" which is quite odd.See the logs from the
validators action I captured. I...
I digged into the issue (I was able to enable debug logging for shared
validators used in the actions sequence for my worker) and my findings
are:- The asset-compute service invocation from AssetCompute Devtool
works fine- The service calls my worker, but the
/adobeio/shared-validators-v1/headless throws 403 as my input IMS Org Id
doesn't match to something - seems that it tries to match to string
"true", see the log I captured. I obfuscated sensitive data and my
actual organization. Most import...
Hi. I found out that I can init firefly app for assets compute workers.
So I did created firefly project in io console having assets-compute
APIs added. Then I was able to init my new project using AIO CLI that
generated for me simple worker that simply creates rendition by copying
source asset.Local tests went fine. I run worker locally thanks to the
aio-cli-assets-compute, i can run assets compute devtool. However, I
couldn't test my worker wither locally or once deployed to io runtime.
Hi,I recently updated AIO CLI together with all my plugins and now I'm
unable to run or deploy any app as it fails fast with the error message:
"Could not locate the bindings file"For instance, running aio app:run
I'm getting error like belowaio app:run
@adobe/aio-cli-plugin-auth:upgrade-config-hook:debug hook running.
Error: Could not locate the bindings file. Tried: →
Hi,I'm struggling to find the information what's the TTL of Audiences
created in People service. By TTL I mean how long a given visitor has
Audience membership once he/she falls into it.Segments created in AAM,
has a pretty clear definition of it, and TTL can be controlled on traits
level. But I'm not sure how it works for Experience cloud audiences.
Does it have some default expiration ?Thanks
I can confirm too that Tag Garbage collector does not remove or fix
references to the tag on pages. The only think it does is to remove old
location of Tag after it was moved. It simply checks if tag from old
location is still referenced on the pages, if not it removes that tag -
that means the OOTB approach for this is that author is responsible to
re-tag all the affected pages (remove tag that was moved/renamed and tag
using that tag once again - but this time the new location of tag will
Hi,I have a question. Let assume my organization id is
123456789@AdobeOrg. However, during implementation of Visitor ID on the
page (not using DTM/Launch), a JS responsible for getting the Visitor ID
uses wrong orgId, e.g. 999999999@AdobeOrg. At first glance, looks like
the analytics tracks the user behaviour correctly. Any idea what damage
this error could cause ? What if I fix the OrgID to use the proper one
Hi,I recently started playing with Customer Attributes available in
Profiles & Audiences of Marketing Cloud. I've noticed that once my
Customer Attribute Source is created an corresponding Data Source is
created in Audience Manager.Is it possible to create traits in AAM using
that Data source, and then create Segment that can be used in Target
?Let's imaging following scenarioUploaded customer attributesCreated
trait based on that attributesCreated segment based on above traitThen
use that Segme...