[idanlodzki]

Documents the new Don't wait for a response switch on HTTP actions (OpsiMate/OpsiMate PR "HTTP actions can send without waiting for a response"): what "sent" means, which failures are still reported, Send test behaviour, the 5 minute response window, the sent metric outcome and the config.fireAndForget API field.

Docusaurus build passes.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Documented the optional “Don’t wait for a response” mode for HTTP actions, including when a run is reported as sent and how receiver status codes and redirects are logged.
  • Clarified that failures before a request is sent still fail the run, and that Send test confirms only that the request was sent.
  • Specified that these runs are counted as sent rather than successful, while the default behavior waits up to 10 seconds for a response.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation-opsimate-docs2	Ready	Preview	Oct 15, 2026 4:26pm UTC

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: OpsiMate/documentation/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 20e8e89f-32c4-4d91-b415-ea45682d593e

📥 Commits

Reviewing files that changed from the base of the PR and between 4de79ec and b029ce5.

📒 Files selected for processing: 1

• opsimate-docs/docs/alerts/actions.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The HTTP action documentation adds the optional Don't wait for a response setting. It describes the setting’s connection behavior, failure conditions, test behavior, metrics outcome, and API configuration.

Changes: HTTP action documentation

Layer / File(s)	Summary
Document fire-and-forget behavior opsimate-docs/docs/alerts/actions.md	Documents the optional setting, including the handoff success condition, connection failure limits, test behavior, metrics outcome, and config.fireAndForget: true API setting.

Priority: ⬇️ Low

Change: Other

Merge Risk: ⚪ Minimal · up to b029c

The docs explain that HTTP actions can report a run as sent without waiting for the receiver. This checkout does not include the runtime implementation to verify those details, but no specific documentation mismatch or other actionable merge risk was established.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}