Troubleshooting

• the request is hitting POST /api/v1/transactions
• the x-api-key header is present
• the idempotency-key header is present
• the payload is valid JSON
• the organization API key is active

• the transaction is ingesting successfully
• the payload includes enough context for the relevant controls
• thresholds are configured appropriately
• the test traffic is suspicious enough to trigger monitoring logic

Login checks

• the account exists in the correct environment
• the password is correct
• MFA is completed if enabled
• the invite was accepted if the user was onboarded through an invitation

Invite checks

• the invite is still active and not expired
• the environment base URL is configured correctly
• the user is opening the latest regenerated invite link

Password reset checks

• the reset token is valid and not expired
• the user is completing the flow in the correct environment

• whether the institution is genuinely low volume
• whether source systems stopped forwarding events
• tenant traffic trend and last successful ingestion time in the internal admin console

• repeated 5xx responses
• sustained ingestion failure
• no traffic after a confirmed client release
• alert or case workflows failing after successful ingestion