Clone issue

Question

Clone issue

Alon Keilin 141

I created working Logic apps. I want the clone to work in the same way that the Logic Apps I cloned work, that is, whenever an alert of the type set to it is triggered, the playbook will run.

Currently, the clone is not running at all and is enabled.

The original Logic apps run every time an alert is raised. Therefore, I do not understand why the clone does not work that way.

Is there anything else that needs to be set up when doing cloning?

Kamlesh Kumar 3,866 Reputation points

2022-07-06T15:43:24.427+00:00

Hi @AlonKeilin-9495 ,

Welcome to Microsoft Q&A Platform. Thank you for the question.

Please provide some more details here, like what is your trigger type and do you see anything in Trigger History?

The process you followed to clone the LogicApp seems correct.

Regards,
Kamlesh Kumar
BizTalk Techie

Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is How

Want a reminder to come back and check responses? Here is how to subscribe to a Notification

If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators
Alon Keilin 141 Reputation points

2022-07-06T15:52:21.063+00:00

I do see in the trigger history but It runs only when I do it manually. That is, when I go into the alert and choose "run playbook" and then choose the playbook in question.

And the trigger type is "When alerts from the CloudApps received"
Kamlesh Kumar 3,866 Reputation points

2022-07-06T16:08:20.683+00:00

Is it possible to share the trigger and flow design, I'll try to replicate the issue. Because with blob connector I am not seeing any issue when cloning the LA.
MayankBargali-MSFT 70,936 Reputation points Moderator

2022-07-08T05:22:53.613+00:00

@AlonKeilin-9495 Thanks for reaching out. Can you share more details on your workflow trigger and action? It looks like your trigger might be configured with the same value that may be causing this behavior or your clone logic app might have not configured correctly.

Accepted answer

0 additional answers

Your answer

Kamlesh Kumar 3,866 Reputation points

2022-07-06T15:43:24.427+00:00

Hi @AlonKeilin-9495 ,

Welcome to Microsoft Q&A Platform. Thank you for the question.

Please provide some more details here, like what is your trigger type and do you see anything in Trigger History?

The process you followed to clone the LogicApp seems correct.

Regards,
Kamlesh Kumar
BizTalk Techie

Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is How

Want a reminder to come back and check responses? Here is how to subscribe to a Notification

If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators
Alon Keilin 141 Reputation points

2022-07-06T15:52:21.063+00:00

I do see in the trigger history but It runs only when I do it manually. That is, when I go into the alert and choose "run playbook" and then choose the playbook in question.

And the trigger type is "When alerts from the CloudApps received"
Kamlesh Kumar 3,866 Reputation points

2022-07-06T16:08:20.683+00:00

Is it possible to share the trigger and flow design, I'll try to replicate the issue. Because with blob connector I am not seeing any issue when cloning the LA.
MayankBargali-MSFT 70,936 Reputation points Moderator

2022-07-08T05:22:53.613+00:00

@AlonKeilin-9495 Thanks for reaching out. Can you share more details on your workflow trigger and action? It looks like your trigger might be configured with the same value that may be causing this behavior or your clone logic app might have not configured correctly.

Answer 1

In case someone faces the same issue then please validate if the trigger and trigger condition are same on both your workflow that would cause this behavior. There could be a scenario that only workflow will get executed based on the trigger that you are using in your workflow. Try to disable the other logic app to confirm if this is not the case and verify the trigger history if you still failed run or the skipped run. In case if you still observe the same behavior then please create a new issue and tag me in so we can connect offline so I can review and assist you further.

Share via

Clone issue

0 additional answers

Your answer