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...

Already sorted out. I was using Node 14.6.0. Swithing back to 12.x solved the issue

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 be s...