Trying to get the BYOC edge to handle our HTML email templates without stripping the signatures, but the flow can’t parse the body right. Does the edge support HTML rendering out of the box? It’s just coming back null for the canned response variable.
Error: 408 Request Timeout
Action: Email.Parse
The 408 timeout happens because the platform waits for a synchronous HTML render that the BYOC edge doesn’t handle natively without the correct CONTENT_TYPE_HEADER and PARSE_MODE set in the EMAIL_ACTION_CONFIG. You’re probably pushing the flow through a standard DEPLOY_PIPELINE and missing the SCHEMA_VERSION tag on the TEMPLATE_PAYLOAD. The validator strips the HTML body when it doesn’t see the explicit HTML_RENDERING_FLAG enabled in the action definition. You don’t need to rewrite the whole routing logic, just patch the EMAIL_PARSE_ACTION with the right headers and bump the FLOW_VERSION before you push it. Compliance rules also require the RATE_LIMIT_POLICY to stay under 500 requests per minute or the edge blocks the CANNED_RESPONSE_VARIABLE entirely. Here’s the exact payload you’ll need to fix the BYOC_ENDPOINT_CONFIG and stop the timeout loop.
curl -X POST "https://api.mypurecloud.com/api/v2/architect/email/actions" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"name": "HTML_Template_Parser",
"description": "Parses HTML email bodies with signature retention",
"version": 2,
"configuration": {
"endpoint": "https://byoc-edge.internal/email/parse",
"contentTypeHeader": "application/html",
"parseMode": "async",
"htmlRenderingFlag": true,
"schemaVersion": "v2.1.0"
},
"scopes": ["email:action:write"]
}'
The header fix makes sense. When the TEMPLATE_PAYLOAD drops, the queue activity view shows zero handled emails. Does anyone know which metric actually tracks the parse timeout?
{"action": "email_parse", "status": "timeout", "body": null...
It’s just stripping the signature anyway.