Work with support

# Work with support

Canonical: https://docs.flowrelay.app/recover/support-signals/
Markdown: https://docs.flowrelay.app/recover/support-signals.md

Support work starts from receipts, diagnostics, and safe summaries instead of copied event bodies, authentication headers, or screenshots of private data.

## Support path
Use this order when another team needs evidence.
1. Use receipts and diagnostics first when a partner or FlowRelay support needs evidence.
2. Share a diagnostics share only after preview and explicit confirmation.
3. Use redacted support summaries and support codes instead of copying private logs or event bodies.
4. Monitor event history, receipts, usage meters, and diagnostics state inside FlowRelay when checking whether a workflow needs attention.

## What to send support
Start with the receipt ID, support code, diagnostics share, affected endpoint, approximate time window, and a plain-language description of the intended Shopify Flow workflow.


## What not to send
Do not share endpoint secrets, authentication headers, HMAC values, tokens, raw event bodies, customer records, Shopify sessions, store passwords, or database URLs. Do not send production screenshots containing private values.


## Alerts and notifications
FlowRelay does not send or configure external alerts - no PagerDuty, Slack, email, or webhook notifications, and no custom alert rules. Use event history, receipts, usage meters, and diagnostics to review operational status.


## Related
- [Share diagnostics](https://docs.flowrelay.app/recover/diagnostics.md)
- [Event history](https://docs.flowrelay.app/operate/event-history.md)
- [Usage limits](https://docs.flowrelay.app/operate/usage-limits.md)

## Safety Boundary
Do not share endpoint secrets, authentication headers, HMAC values, tokens, raw event bodies, customer records, Shopify sessions, store passwords, or database URLs in public examples.