CODEWITHSUNDEEP
emailtriggersazure-logic-apps
ingo_ww
ingo_ww

Reputation: 321

logic Apps : What are possible reason that an new-email-trigger does not fire or failed?

The office365 trigger when new -email arrives (V3) is my logic Appp trigger condition.

The workflow does following:

  1. Triggered on incomnig e-mails
  2. check if sender is an AD User, if not send to a special Mailaddress
  3. analyse the subject and put informations gother in new mailboydies and distribute the mail to other mailboxes

I have seen a few cases I don' t understand, what it is the reason for that.

  1. I got a trigger sicceeded but the trigger doe not fired Why?

    image1: trigger History

    last not fired triger image 2: not Fired Triggers Screenshot shows succeeded triggers but not fired to start a run. In this time spawn there was no email in the inbox.

  2. I got a trigger failed ( i cannot reconstruct which mail could the reason).

    failed Trigger image3: failed Trigger for this case I can say nothing i found no e-mail at this time, but it is possible that there was through Dectivation/Activation of logic app old not readed mails ttries to trigger. it was the first trigger after creation of this Logic app for testing (copied from other subscription).

Can someone say me possible reasons for this 2 situations?

Upvotes: 0

Views: 1713

Answers (1)

Hury Shen
Hury Shen

Reputation: 15724

A status of skipped just indicates that the nothing new was found to fire the logic. Because the trigger will do check operation every once in a while even though the mailbox do not receive new email.

I think you do not need to worry about the records under "Trigger history". You just need to check the records under "Runs history". The records under "Runs history" can give a more intuitive picture of what's your logic app going on.

Upvotes: 1

Related Questions