Azure Logic App Blob触发器在子文件夹下未触发问题咨询

Hey there! I’ve run into this exact issue before, so let’s get your trigger firing for those dynamic subfolders in no time.

Here’s what you need to check and adjust:

• Update the Blob Path with Recursive Wildcards
  By default, the Blob trigger only listens to the container root if you don’t specify a path pattern. To cover all dynamic subfolders (and any new ones you add later), set your trigger’s Blob path to {your-container-name}/**. The ** wildcard tells the trigger to recursively scan every subfolder under the container, so files like mysubfolder/mynewdocument.txt will trigger the logic app just like root-level files.

• Enable "Include Subfolders" (if available)
  Depending on the version of the Blob trigger you’re using, there might be a checkbox labeled Include subfolders in the trigger settings. Make sure this is checked—it explicitly tells the trigger to look beyond the root directory for new blobs.

• Verify Path Pattern Specificity (if needed)
  If you only want to target a certain level of subfolders (not all recursive levels), you can use a pattern like {your-container-name}/*/* for first-level subfolders. But since your subfolders are dynamic and changing, ** is the most flexible choice here. Just double-check there are no extra slashes or typos in your path—small mistakes can break the pattern matching.

• Test and Troubleshoot
  After updating the settings, save your Logic App and upload a test file to a subfolder. Keep in mind triggers can have a small delay (usually a few seconds to a minute) before firing. If it still doesn’t work, check the Logic App’s Run History for any error messages—common issues include missing permissions for the Logic App’s managed identity to access the blob container.

内容的提问来源于stack exchange，提问作者Thomas