Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow context changes after calling a campaign workflow #195

Open
Ricorei opened this issue Sep 6, 2021 · 0 comments
Open

Workflow context changes after calling a campaign workflow #195

Ricorei opened this issue Sep 6, 2021 · 0 comments
Labels

Comments

@Ricorei
Copy link

Ricorei commented Sep 6, 2021

When doing:

effect("run_workflow", args, "o", "_documentRefresh") -- 1 
effect("run_workflow", args, "c", "_itemLock")  -- 2
effect("run_workflow", args, "o", "_documentRefresh")  -- 3

-- 1) Works nicely.
-- 2) Works nicely.
-- 3) Suddenly doesn't work as nicely.
  1. Call workflow -> ActiveCampaign
  2. Call workflow -> Object

The 2nd workflow will look into the Active Campaign and not in the Object resulting as:

  1. Call workflow -> ActiveCampaign
  2. Call workflow -> [Object] ActiveCampaign instead of [Object] Current Item.

https://imgur.com/a/3zsJavT

On this screenshot and as a proof/example, _documentRefresh isn't found unless it's created in Active Campaign. Though every Object variable "o" created in the campaign workflow will be correctly assigned to the current running item.

Perhaps the behavior is on purpose but it seems counter intuitive.

@Solanya Solanya added the bug label Jan 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants