Inspect logs and delivery outcomes

Open Usage to inspect template processing and related activity. Keep the request ID, template ID, timestamp, and Slack message coordinates together when investigating a problem.

Choose the right record

Question	Where to look
Did compile/send succeed, and were credits used?	Credit/usage entry and its detail
Did Slack deliver a button click?	Interaction history filtered by action ID and message
Did my receiver process a webhook?	Interaction component outcome plus the receiver’s own records
Did a message update succeed?	Related message activity and update component
Why did a scheduled message or digest not send?	Schedule/queue state and its execution/batch history

A successful HTTP response from an asynchronous operation can mean accepted work. A closed modal means its receipt was saved. Neither alone proves final delivery.

Investigate one message

Find the originating send using its template and time, or your application’s request ID.
Save the returned channel and message_ts.
Inspect interactions for those coordinates and the relevant action_id.
Check each component separately: webhook delivery can succeed while a message update fails.
Correlate modal delivery with submission.id or the receiver’s X-LithoBlocks-Submission-Id header.

Interpret failures

Outcome	Next step
Validation failure	Read the affected block/field and compare the input schema
Missing scope	Grant the endpoint’s required scope with an eligible role
Slack channel/user error	Check the connected workspace, destination ID, and private-channel membership
Receiver 400	Compare the rendered payload with the receiver’s schema
Receiver 401/403	Verify destination headers and receiver permissions
Receiver 5xx	Inspect receiver logs before retrying
Timeout or `uncertain`	Reconcile the receiver outcome; do not assume nothing happened
Pending	Check whether work is still waiting for asynchronous delivery

API visibility and data handling

GET /v1/interactions and GET /v1/interactions/{id} expose sanitized outcomes and timing, not arbitrary webhook request/response bodies, raw keys, or URLs. Modal-submission records can contain entered values. Access is organization-scoped. Retention and export availability depend on the configured service policy. Do not rely on a guaranteed 90-day history or a CSV export button. Keep operational records needed by your own application, minimize sensitive input, and ask support about retention requirements. When contacting support, include the environment, request ID, timestamp, template ID, and machine-readable error code. Redact keys, tokens, and personal form data. Interaction API and click tracking · Security and data · Troubleshooting

​Choose the right record

​Investigate one message

​Interpret failures

​API visibility and data handling

Choose the right record

Investigate one message

Interpret failures

API visibility and data handling