Edit: The event repeating is expected behavior, the same way it goes for loading data from Bubble’s server via .get().
I could definitely use some help here. Doing some tests, my setup is as follow:
Bubble workflows -
Both actions are client side and the code in each action is -
First action:
function(properties, context) {
console.log("first message in sync code under Async with context.async action (first workflow action)");
const asyncFunction = async () => {
let response = await fetch("https:www.goe.com");
console.log(`second message, now inside async code, the variable is ${response.status} (first workflow action)`);
}
context.async(async callback => {
try {
let result = await asyncFunction();
callback(null, null);
}
catch (err) {
callback(null);
}
});
console.log("third message in sync code under Async with context.async action (first workflow action)");
}
Second action:
function(properties, context) {
console.log("first message in sync code under Async withOUT context.async action (second worflow action)");
const asyncFunction = async () => {
let response = await fetch("https:www.goe.com");
console.log(`second message withOUT, now inside async code, the variable is ${response.status} (second workflow action)`);
}
asyncFunction(); //simply calling it without async.context
console.log("third message in sync code under Async withOUT context.async action (second workflow action)");
}
Then the resulting order of events isn’t what I expected. The synchronous code before context.async repeats, it’s the “first message”. Why is this?
Take a look don’t mind the big blue Bubble log:
The second workflow action goes as expected, with synchronous events happening first then the asynchronous one happening after.
@shot pinging you because I don’t want to clutter that other thread. Any thoughts on this?
P.S: I used your template on this one.
P.P.S: It’s supposed to 404, not trying to actually fetch anything.
Link to the app here and to the editor here.
).