When a File is Created(properties only) not triggering

(0) Share

Report

Posted on by Paul_c5mi

I'm using the "When a file is created(properties only) trigger on a doc lib. The trigger settings are default and no changes/adds were made.

I created this flow in a solution in my dev environment, tested, and then exported/imported to my production environment and made sure everything was turned on. I have other flows in this same solution which are working fine except for this one.

It seems to trigger at random or (most of the time) not at all when I add a file to the doc lib. The flow by the same name in the Dev is turned off and the Production is turned on.

I've walked through all the steps here https://learn.microsoft.com/en-us/power-automate/triggers-troubleshoot with no success.

Is MS having issues? If I turn on the Dev flow it fires instantly but not in the production environment.

I have the same question (0)

All responses (4)

Answers (0)

Sayen Zhang on at

Like (0)

Report

Hi Paul,

Please let me collect information to know more about this issue:

1. Is the flow not triggering only in the production environment? Have you tried to import solution that contains flow in another environment?

2. Can we turn off the flow that in Dev and production environment and then create the same flow in production environment? After we created, is the issue happened again?

3. Do you see the error in the Details? For example

4. Have you noticed if the production environment has difference setting when the flow trigger works or not woks?

Best Regards,

Sayen Zhang

Was this reply helpful? Yes No
Paul_c5mi 5 on at

Like (0)

Report

I have not tried to import the flow into another environment yet but I'll try that today. I will try placing the flow in question into the default but I'm sure it will trigger there.

When I did my testing the Dev environment flow was turned off and the Production version was turned on. At one point I turned the flow off in the Production environment and turned it back on just to see if it would trigger. It did trigger a single time.

I never saw anything in the flow that would indicate the trigger failed like what you show above.

Also, FYI in the solution I imported to the production environment I have other flows in that solution which use modify triggers and these work perfectly.

Was this reply helpful? Yes No
Paul_c5mi 5 on at

Like (0)

Report

So, on the Dev environment I turned the flow on (and turned it off in the production). Added a doc and the flow fired. The other flow I have in the production environment which uses a different trigger works just fine. The trigger on that flow is when a document is modified.

1 people found this reply helpful.

Was this reply helpful? Yes No
Sayen Zhang on at

Like (0)

Report

Hi Paul,

Thanks for your information.

Have you can check plugins or code which is running in your production environment to see if these will make the flow not work?

If you have followed the advice and still not find the impact parts, I suggest you create a support ticket for professional assistance following the below procedure.

Get Help + Support - Dynamics | Microsoft Docs

Best Regards,

Sayen Zhang

Was this reply helpful? Yes No