Yeah that kind of stinks. We recently had to adjust all of our action
CRON triggers for daylight savings. Every time-based trigger shifted an
hour ahead. Anything running at 5am, ran at 4am, etc.
Hard to tell what your end result is meant to be, but you can't "return"
multiple times in a single function. If you're wanting 10 responses of
"Hello ", you'll need to call the function 10 times.Also, if
your action is a web action and is invoked by a web service, the params
object contains a lot more information than just the parameters you're
passing into the function.
We would also like to know this. We are creating custom APIs for clients
leveraging Adobe products we are selling, and would like to keep
namespaces separated. As-is, we have to use packages for each client. It
works, but would we would like more separation between the clients we
service.
Hey there, I've set up an action I'd like to run at 12:30am EST every
night. I've set up my trigger as the following: wsk trigger create
test-t4l \ --feed /whisk.system/alarms/alarm \ --param cron "30 0 * * *"
\ --param stopDate "2021-10-31T23:59:00.000Z" The trigger is created
successfully and when I "get" the trigger, it shows the correct cron
schedule. However, I checked the activation logs this morning and the
action did not run until 4:30am.Am I missing a timezone difference or
something? I...
I have two Runtime actions:1) Get a list (array) of files to download
(filename -> download URL)2) Upload file contents to database. The array
in action 1 contains 200-250 key/value pairs at any given time. Per
key/value pair in the Action 1 array, I invoke action 2 (upload files)
as non-blocking via the OpenWhisk package. I'm also leveraging a 5
second delay after every 10 results to avoid concurrency error. for (let
i = 0; i < filesToUpload.length; i++) { if((i + 1) % 10 === 0 )await
sleep(500...
I'm setting up an API through OpenWhisk with multiple
endpoints:/privacy/jobs/create POST/privacy/jobs/{jobID}
GET/privacy/jobs/files/{jobID} GET/privacy/events/ GET and POSTfor my
POST /jobs/create endpoint, I am getting CORS errors: Access to
XMLHttpRequest at
'https://runtime.adobe.io/apis/****/privacy/jobs/create' from origin
'https://requestdomain.com' has been blocked by CORS policy: Response to
preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is...
*SOLVED. ANSWER BELOW*I am following the documentation for Subscribing
to Privacy Events (found here). Things I have done:1. I have created my
local Node.JS/Express App and linked it to ngrok for a public URL.2. I
have linked my webhook ngrok url to a Privacy Events integration and
verified the challenge. 3. I have set up a "post" route on the root "/"
and am logging the request, however there is no body: app.post('/',
function(request, response) { console.log(request);
console.log(request.body)...
