When did the API workflows started being called "Backend workflows"?

I mean, the name makes sense…

I confess that I still have 10 minutes until my next pomodoro.

8 Likes

So this should create mass confusion on the thousands of forum posts recommending the use of API Workflows! It’s a good move though. API Workflows was a misleading term.

2 Likes

Hello @eve

As @eli mentionned,

suggestion: use Find and Replace on the forum :slight_smile:


Find: API Workflows
Replace: Backend Workflows (previously API Workflows)

Also, maybe add a short title description for newbies (like Reusable elements):

Internal workflows process (I’m not an expert at naming! :sweat_smile:)



2 Likes

Yes, this was a long overdue change on our end, since the scheduler really has nothing to do with the API other than both using backend workflows. (Plus, we may have a new addition to that tab coming soon!). But good point re: the forum confusion. I like the find-and-replace idea, though I want to check to make sure it doesn’t cause more chaos than it solves before pulling the trigger…

14 Likes

Great idea.

Small suggestion: I would change “called” to “previously” to signify it was a name change and not an underground alias!

1 Like

Yay more power to us Bubblers!

5 Likes