I want to use a Microsoft Flow with Trigger by Microsoft Forms.
But, When sening from Microsoft Forms, The Forms does not run.
Only few case or unknown case, The Forms run at history.
In all case, the Forms response exist in Forms results.
Microsoft Flow: 1.0.2244.6.fa49700 Flow-Service.release_20170728 (CY1AZRBLDVM227.170801-1118)
What limit of Microsoft Forms Trigger "When a new response is submitted" ?
Solved! Go to Solution.
You need to add in a action after the trigger
Get Response Details from Microsoft Forms
this video should help - https://www.youtube.com/watch?v=iEm0M_2EP_Y&list=PLN-cZRQeAiDWT0J1NW9sBDEXX3jkKkyjP&index=26
So here you mean not all the responses under the Form are logged into Microsoft Flow?
I will make some tests and update the result here.
This might be related with the form API used under Microsoft Flow:
Adding some reference:
1. Microsoft Forms can submit - Always.
2. Microsoft Forms can view the answer - Alweys.
3. Microsoft Flow run - Rare. less than 10%.
4. Microsoft Flow log run - Rare, less than 10%.
Trigger: Microsoft Forms - When a new response is submitted.
Action: Microsoft Teams - Post message.
I don't use any programming code like C#, Python, etc. and don't use any API like Microsoft Forms API.
Thanks for the udpate.
I suspect this should be related with the trigger, as when I clicking the running details, it will just show me a trigger failed message.
Feedback has been sent on our channel, and I will post back if I got any response.
I got a response tolding that there is a problem with the Form trigger.
Once a skipped happens, the trigger would send a re-try after some delay. and during the delay there would be no trigger fires, which means the trigger will not work during the delay.
The Team is working on this, but currently there is no ETA.
thank you for your reply,
I will re-check Microsoft Form trigger on Microsoft Flow.
Until now, I check over 10 times checking, and the result is very few runs of my Flow.
NOT WORK @v-micsh-msft
Today, test result.
Form 1. A Question of 3 Options.
Form 2. A Question of 1 text input.
1. Trigger. Microsoft Flow - When a new response is submitted
2. Action. Microsoft Teams - Post message
Submit three times for Form 1,
Submit three times for Form 2.
There are no runs.
Can I do anythings ?
Thanks for the update.
There is no further information needed from your side.
I post here just notifying your with the proper information.
The issue has been identiifed, and a fix is working on that.
For current situation, we should wait for the fix to release.
Thank you for your reply.
and I'm waiting for any update.
This scenario is strong one of Flow scenarios.
After fix this issue, I will check, check, check and share with friends/partners/customers.
thank you for your report about this issue.
Yesterday, 0 minutes to 57 minutes, the time between Form submission and Flow run,
Test by 2 tenant and, each 2 forms, over 10 times.
and almost these time over 50 minutes.
I hope any update for this issue.
I share a flow for test this issue.
This flow can notify the time to your phone after submittion Forms.
@mache, sorry, I don't have any workarounds. Mine just started working. I guess it is possible that the fix/update hasn't been pushed to all of the users yet. I'm not really sure though.
I have a flow which triggers when a record is created on my Dynamics 365 CRM for the entity 'Planner'. The subsequent action to follow creates a task in Planner. The problem is the inconsistency of the trigger firing off. To test this inconsistency, I created five records on my CRM. The result should have been the creation of five planner tasks. Instead, only two of the five planner tasks were created. Is the fix currently under development or is it a problem on my end?
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Many congratulations to the Season 1 2021 Flownaut Crew!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.