Common Issues

Quick fixes for the issues teams hit most often when setting up AgentPulse.

401 Unauthorized when sending runs

The Bearer secret is missing, malformed, or was rotated. Confirm the Authorization: Bearer <secret> header is present and matches the agent's current secret. If the secret was lost, rotate it from the agent settings and update your environment.

Runs not appearing on the dashboard

• Check the response code — a 2xx means it was accepted; a 402 means the monthly run limit was reached.
• Confirm you are viewing the right product and period (24h / 7d / 30d).
• Make sure status is exactly success or error.

Alerts not firing

• The rolling window may not have enough runs yet to evaluate the metric.
• The rule may already be in an open state — alerts deduplicate and only re-arm after the condition resolves.
• Confirm a channel is attached and configured. See Notifications.

Hit a plan limit

Creating a product, agent, or channel beyond your plan is rejected, and ingestion past the monthly run cap returns 402. Review your plan limits or upgrade to Pro.

Still stuck?

Email engage@sentinelflux.in with your organisation name and what you are seeing.