Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Runbook: TOTVS Fluig — Start / Stop
| Field | Value |
|---|---|
| System | TOTVS Fluig |
| Owner | (responsible squad) |
| Estimated time | (fill in) |
| Maintenance window required? | (Yes / No) |
Initial checks
- Confirm production access
- Verify change ticket is open (if applicable)
- Notify team in tech-incidents (for P1/P2)
Start procedure
Step 1 — Verify pre-conditions
(Describe what to check before starting the system.)
Expected result: (fill in)
Step 2 — Start the system
(Describe the steps to start the system — commands, console access, etc.)
Expected result: (system responding normally)
Step 3 — Health check
- (check 1 — e.g., health endpoint returns 200)
- (check 2 — e.g., logs show no critical errors)
- (check 3 — e.g., integrations responding)
Stop procedure
Warning
Planned stop: Only stop outside a maintenance window in case of emergency.
Step 1 — Notify users
(How and when to notify users about the maintenance.)
Step 2 — Stop the system
(Steps to gracefully stop the system.)
Step 3 — Confirm stop
- (confirmation 1)
- (confirmation 2)
Quick troubleshooting
| Problem | Solution |
|---|---|
| System won’t start | Check logs at (where) |
| (problem) | (solution) |