Release Update – 2016-11-18

Release Notes:

  • Confirmation dialog added to resubmit run
  • Singleton triggers allowed (can mark a trigger with operationOption of singleton, and new instances will not fire unless all running flows are completed)
  • Can now view the raw inputs and outputs of actions with the historical run view
  • Performance improvements for spliton (debatch) triggers
  • Connection verify in designer for supported connectors

New Connectors (rolling out globally):

  • Azure Document DB
  • Cognitive Services Face APIs
  • Disqus
  • Chatter
  • Power BI
  • Google Calendar
  • Google Tasks
  • Pinterest
  • HipChat
  • WordPress

Bug Fixes:

  • Margins would sometimes cut off part of the output picker
  • Error message improvements on invalid operations
  • Message wasn't shown for actions skipped in a foreach loop
  • Accessibility improvements


Comments (10)
  1. I guess Microsoft Teams is on top of your priority now 🙂

    1. We are actively working with that team as we would love to see that connector too 🙂

  2. Gert Vloo says:


    do you have a example of the singleton option? How can I use this? I don’t get it to work.

    1. “triggers”: {
      “mytrigger”: {
      “type”: “http”,
      “inputs”: { … },
      “recurrence”: { … },
      “operationOptions”: “singleInstance”

      Updating docs now and we are also working on exposing this in designer

      1. Gert Vloo says:

        Thanx for the quick reply.

        I’ve an other question about a topic trigger in logic apps what I will combine with the singleton option.

        When I choose for batches of messages I still get one logic app instance per topic message.
        In my configuration I have removed the split-on tag so I can loop over the messages within my logic app.
        Can you explain why I get a array with one message and multiple Logic app instances?

        1. Yes so spliton is used to debatch arrays into an individual run per item. So twitter for instance returns an array of new tweets, so when a spliton is added to trigger will split the array into one run per tweet so user can process each item individually. Unfortunately the singleton option doesn’t yet support spliton (as it would need to potentially queue and process each item one at a time). However with Service Bus this should be easy as there are actually 2 separate triggers for each operation. “When a message is received” will only return one message at a time (And therefore not need spliton). “When one or more messages is received” returns a batch of all messages, and uses spliton. For singleton, just make sure you use the “When a message is received” one and you won’t need to remove spliton or work with an array.

          1. Gert Vloo says:

            Hai Jeff,

            again thanks for the reply. Unfortunately not an anwser for my problem. What I try to do is setup a message train pattern. Therefor I want to use a singleton logic app, and get all messages from the queue as trigger. Than in de logic app loop with a foreach over the messages. I remove the split-on and at the SingleInstance option. But what happens is that the is just one message in the array.

            I hope you have a solution.

          2. Ah ok – yes should work as you want – can you send me an email with details and I will loop in the devs who work on the Service Bus connector to help investigate. jehollan[at]microsoft[dot]com

  3. James Riker says:

    Where is the updated documentation on how to implement the Singleton trigger? I can’t see anything in the workflow definition language that shows how this is done.

    1. “triggers”: {
      “mytrigger”: {
      “type”: “http”,
      “inputs”: { … },
      “recurrence”: { … },
      “operationOptions”: “singleInstance”

      Updating docs now

Comments are closed.

Skip to main content