Forum Discussion
Advocate ICannot create an alert with error Request failed with status code 500
Hi,
When I attempt to set up an alert within Fabric, it fails with a "Request failed with status code 500" error. What am I missing here? I just tried a simple step where I set an alert for when an item (Notebook, in my case) executes successfully. I have admin access on the workspace.
Hi v-kpoloju-msft , Thank you for the solutions you provided. Unfortunately, none of them worked. I tried sending an email, which did go through, but team app messages still aren't functioning. I found an app called Fabric Activator that needs to be added to Teams, and I'm currently seeking approval for it. Please let me know if you think I'm not on the right track with this solution or if you would like me to try something else.
6 Replies
PraveenVeliAnd also i get below error when i click Send me a test action.
It works for sending an email to Outlook but does not work for Teams message.
v-kpoloju-msftCommunity Support
Hi PraveenVeli,
After going through the information, you gave me, I have listed the alternative workarounds that can possibly fix the problem. Follow these steps:
A 500 Internal Server Error typically indicates a problem on the server side. However, some client-side misconfigurations can also trigger this issue.
- Even though you do have admin, ensure that you have the correct permissions in Fabric to be able to create an alert. You should have the correct Fabric role (e.g., Admin, Contributor) in the workspace.
- Since you are writing an alert for a Notebook, try to use another resource like Dataflow or Pipeline to determine if the issue is Notebook-specific. If you are utilizing a Fabric capacity, ensure it is not throttled or overloaded.
- Try a different browser or incognito mode. Delete cache and cookies and retry again. If it is possible, check the Developer Console of the browser (F12 → Network tab) and see if the API requests are failing. Examine failed requests and see if there is some detailed error message.
Additionally, I have identified some workarounds for the second issue mentioned below:
- Make sure the integration with Microsoft Teams is properly set. Check the setting and ensure the Teams channel and webhook URL are correct.
- Manually test the webhook URL for its functionality. Postman or similar tools may be used to send a test message to the webhook URL and check for success.
- Make sure the Teams bot or app is given permission to post messages to the channel since permission issues might occasionally interfere with message delivery.
- Double-check the recipient's email address format in the Teams action using the complete email address rather than a username. Verify for any policy limitations as well, since automated Teams messages are blocked by some organizations.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.Best Regards.
- v-kpoloju-msft
Hi PraveenVeli,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
- PraveenVeli
Hi v-kpoloju-msft , Thank you for the solutions you provided. Unfortunately, none of them worked. I tried sending an email, which did go through, but team app messages still aren't functioning. I found an app called Fabric Activator that needs to be added to Teams, and I'm currently seeking approval for it. Please let me know if you think I'm not on the right track with this solution or if you would like me to try something else.
- PraveenVeli
Adding the Activator app to the teams did the trick. Once it's added i started getting messages.