Is it possible for a workflow to allow multiple triggers? For example an HTTP request but also an incoming email?

Help
,
20

Nacho Caballero : Chrome in OSX. Let me try in incognito mode in case it’s due to an extension

21

Nacho Caballero : Yeah, I’m not seeing it in incognito mode, so it’s probably one my extensions. Sorry about that

22

Dylan Sather (Pipedream) : np

23

Nacho Caballero : In case someone else reported it, apparently it’s the Web Clip feature in OSX: Why am I getting error for apple-touch-icon-precomposed.png - Stack Overflow I use Chrome and I get these 4 requests every time I create a new http trigger

24

Nacho Caballero : since I often start with an HTTP trigger, it’s usually not a problem, but if I have a cron trigger, build the workflow and later change it to an HTTP trigger, it may cause some unwanted side effects. I’m surprised no one else has reported it

25

Dylan Sather (Pipedream) : I’m still not sure why your browser would make the HTTP request to these files on trigger creation, I’m still not able to replicate that specifically

26

Dylan Sather (Pipedream) : the Pipedream UI itself shouldn’t be making HTTP requests to the endpoint URL, trying to figure out why that might be happening

27

Nacho Caballero : Are you on OSX?

28

Dylan Sather (Pipedream) : I am, using Chrome

29

Nacho Caballero : Ok. I’ll double check my extensions just in case

30

Nacho Caballero : I finally figured out why I was getting those 4 GET requests!! :sweat_smile:

31

Nacho Caballero : It’s my clipboard manager’s fault (https://pasteapp.io/). Whenever I copy a URL, it hits it with 4 GET requests to show me something like this

image.png

32

Nacho Caballero : I’ve disabled “show link previews”, so this should no longer happen

33

Nacho Caballero : Although I’m still not sure if this was related to the multiple events when creating sources

34

Dylan Sather (Pipedream) : wow! Good find.

35

Dylan Sather (Pipedream) : this might make sense re: why you were seeing multiple events with the task scheduler source:

  1. Copy URL
  2. Multiple, simultaneous requests get made to the URL
  3. The first HTTP request made to the source triggers this block, which subscribes the source to its own self channel for the purpose of queueing up scheduled tasks. This is the race condition - if multiple requests arrive simultaneously the first time the source is triggered, isSubscribedToSelf will be false, and that block will run multiple times
36

Nacho Caballero : ah, that makes sense

37

Nacho Caballero : This wasn’t the reason why the /cancel action doesn’t work, right?

38

Dylan Sather (Pipedream) : You can give cancellation a try again but that’s correct, there’s still a separate bug with that we need to fix

39