Freshservice incident
Workflow Automator Web Requests Returning 400 Errors
Resolved after 10 hours 49 minutes, affecting Workflow and Workflow, on September 28, 2026.
The issue has been resolved and the affected services have been restored. All functionality is now operating as expected.
Affected components
Update timeline
- investigating Sep 28, 2026, 07:39 AM UTC
We are currently investigating an issue where Web Request nodes in Workflow Automators that use external URLs are returning HTTP 400 (Bad Request) responses. This is impacting workflows that rely on these external API/web requests and may result in workflow execution failures.
- identified Sep 28, 2026, 03:30 PM UTC
Our team has identified the issue and is actively working on a resolution. We are currently implementing the necessary fixes to restore normal service. We will provide another update once the fix has been implemented.
- identified Sep 28, 2026, 04:02 PM UTC
The issue was resolved for the US regions at 9:32 PM IST, and Our team is continuing to work on the EUC region and will provide further updates as we make progress.
- resolved Sep 28, 2026, 06:28 PM UTC
The issue has been resolved and the affected services have been restored. All functionality is now operating as expected.
Your product runs on more than Freshservice
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services