My trigger http://func-xxx-app-name-xxx.azurewebsites.net/api/xxx is not working any more

To troubleshoot the issue with your trigger not working, consider the following steps:

1. Check for Errors: Review the details of your flow in Power Automate to see if there are any error messages related to the trigger. This can help identify if the trigger is failing due to connection issues or other problems.
2. Verify Connections: Ensure that the connections used in your flow are still valid. Sometimes, connections can expire or be revoked, which would prevent the trigger from functioning properly. You can check this by going to the Connections section in Power Automate.
3. Inspect Trigger Conditions: If your trigger has specific conditions that must be met, verify that those conditions are still valid and that the data in your supporting table meets those conditions.
4. Data Loss Prevention Policies: Check if any Data Loss Prevention (DLP) policies have been implemented that might affect the trigger. If your flow violates a DLP policy, it can be suspended, preventing the trigger from firing.
5. Modify and Save the Flow: Sometimes, simply editing the flow and saving it again can help re-register the trigger. After making any necessary changes, save the flow and see if the trigger starts working again.

If these steps do not resolve the issue, you may need to further investigate the specific configuration of your flow and the supporting table to identify any changes that might have occurred.

References:

• Troubleshoot common issues with triggers

Hi @Kaevikj Katerina .

Please try below to troubleshoot and potentially resolve the problem:

1. Check for Runtime Errors: Sometimes, the function runtime might not start due to exceptions. If you have Application Insights enabled, you can run the following query to check if there are startup exceptions logged:

      
      exceptions
      
      | where customDimensions.Category == "Host.Startup"
      
   

2. Review Function Invocation Logs: It’s possible that the function was triggered but failed during the execution. You can use the following query in Application Insights to investigate:

      
      exceptions
      
      | where customDimensions.prop__functionName =~ "*MyFunctionName*"
      
   

3. Check Competing Triggers: If there are multiple function apps trying to pull messages from the same queue, one may interfere with the other. Ensure that there aren't other functions configured to trigger on the same source.
4. Query Application Logs: If you've set up a Log Analytics workspace, try querying the logs to get detailed insights:

      
      AppServiceConsoleLogs_CL
      
      | where AppName_s =~ "*MyFunctionAppName*"
      
      | where Log_s contains "FunctionAppLogs"
      
   

5. Inspect Connection String or Queue Configuration: If the trigger relies on connections from a table, double-check if there have been any changes in connection strings or configuration that might affect your function.
6. Confirm Trigger is Configured Correctly: Ensure that the trigger is still correctly set up in your environment. Sometimes, changes in the cloud service or app configurations may require adjustments to how triggers are handled.

I hope this helps you get your trigger back on track! If you have any more questions, feel free to ask.

References:

• Investigating and reporting issues with timer triggered functions not firing
• Learn about using Application Insights to monitor Azure Functions
• Using Log Analytics with Azure Functions

Dear Mishra,

Thanks for your effort to provide me with solution.

The problem was that my client secrete certificate was expired. After renewing and replacing the key it start working.

Regards,

Katerina