Hey @matenauta, an n8n execution does not know what happened in a past execution. So if you want to make sure that your path B is being used in the next execution after path A has executed, you need to store this information after executing path A.
You could use pretty much any external storage for this, just make sure to update this information after each path you execute and read it at the beginning of your workflow.
You can also use n8n’s static workflow data for this, but this is a bit tricky as it won’t work for manual executions.
I’ll check this out because I’m using N8N for replace Zapier/Make and I’ll try to build almost everything automatically and not manual.
Of course, now I’m testing with manual triggers but definitely I’ll need to move and it seems to be cool to get deep into that
I’ll try to jump the tricks by myself but I’ll ask for direction if I get stucked.
I will share all my workflows (Discourse, OpenAI, Budibase, Mailgun and Kelia (a few manual webhooks and http requets) when they will be ready for production