Live triage demo The alert says Flow failed. Triage decides whether that is even true. Which flow · which element · how to act — then: is it ours at all? All personas
NW
Home
DMs
Activity
Northwind Trading
Search Northwind Trading
Channels
# flow-ops-oncall 1
# integrations
# erp-support
# spring-campaign
Direct messages
Flow agent
● Priya
● Integrations on-call
# flow-ops-oncall 14
Thursday, March 12
Flow Builder Order_Fulfillment_Sync v9 · ActiveRecord-triggered on Order
Auto-Layout 47 faults · 1:12–3:40 AM Active Run Debug View Tests Save As New Version Save Activate
Opened from #flow-ops-oncall at the element that threwRun 4a91f2c · 47 runs faulted between 1:12 and 3:40 AM, and every run since has been clean · nothing on this canvas has been changed Read only
Order status is FulfilledStart
Run Immediately · 47 faulted overnight
+
Order_Payload_BuilderSubflow · v3Clean every time · returned a valid payload
+
Push_Order_to_ERPAction · ApexFailed 47× · HTTP 503 from the callout
Flow ran as authored · the cause is below this element
Not on this canvas — three levels the platform cannot draw
3ErpOrderPublisher.publish()Apex · threw CalloutException
4POST /v2/ordersNamed Credential NetSuite_Prod · 503
5NetSuite productionExternal system · no visibility
This is why the alert said unknown error. Flow reported the failure because it is the caller, not because it is the cause.
+
Notify_Fulfilment_TeamActionNot reached 47×
EndEnd