Skip to main content
Skip table of contents

US Hours Escalation Workflow (ERP)

Production Down, Fatal or Stuck Process

  1. The issue should be escalated to Cloudops team (Level-1) by creating a WEDEVOPS ticket

  2. If Cloudops cannot resolve the issue at their end, or believe engineering help is required, then issue should be escalated to the primary On-Call Engineer (Level-2)

  3. If primary On-Call Engineer is not available, then issue should be escalated to the secondary On-Call Engineer (Level-2)

  4. If the On-Call Engineer is unable to resolve the issue at their end, then issue should be escalated to the Dev Manager (Level-3)

Production Critical issues outside of Fatal and Prod Down

  1. The issue should be escalated to the Product team (Level-1) by tagging in Slack (@product-managers) or Jira (Product Managers)

  2. If Product Manager cannot resolve the issue at their end, or believe engineering help is required, then issue should be escalated to the primary On-Call Engineer (Level-2)

  3. If primary On-Call Engineer is not available, then issue should be escalated to the secondary On-Call Engineer (Level-2)

  4. If the On-Call Engineer is unable to resolve the issue at their end, then issue should be escalated to the Dev Manager (Level-3)

To verify who is On-Call, follow the steps from below Confluence page

How to verify who is On-Call

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.