Skip to main content
Post-commit hooks append events to a local spool file rather than making a live network call. A background process then delivers those events to Terma with exponential backoff, so activity data reaches the dashboard even when connectivity is intermittent. The terma spool commands let you inspect the queue and force immediate delivery when you need events to appear right away.

​
How Spooling Works

Understanding the spool lifecycle helps you diagnose gaps in the dashboard and resolve delivery issues quickly.
1

Event appended

When a post-commit hook fires, it writes a spool event to the local queue. No network call is made at this point, so commit performance is never affected by network conditions.
2

Background delivery

A background flush process picks up queued events and delivers them to Terma. If a delivery attempt fails, the process retries with exponential backoff and leaves the event in the queue until it succeeds.
3

Confirmation

Once Terma acknowledges an event, it is removed from the spool. The session and commit data become visible in the dashboard.
The post-commit hook never blocks on Terma being reachable. Commit performance is not affected by network conditions.

​
terma spool status

Show what is currently queued and when the last delivery attempt was made.
The output includes:

​
terma spool flush

Force immediate delivery of all queued events to Terma, bypassing the backoff schedule.
Use terma spool flush after a prolonged outage, after restoring network connectivity, or when you want commits to appear in the dashboard without waiting for the next automatic delivery window.
Check the queue then flush it
If events are stuck in the spool, run terma doctor — it checks connectivity and shows the exact fix command.