Nexeed
    • Introduction
    • User manual
      • Event type
      • Subscription
      • Recipient
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • notification-service/notification-service
      • Migration from previous versions
      • Setup and configuration
        • notification-service/notification-service
      • Start and shutdown
      • Regular operations
      • Failure handling
      • Backup and restore
      • Logging and monitoring
      • Known limitations
      • Service account role grants
    • Developer documentation
      • Concepts
      • How-to
    • API documentation
    • Glossary
Notification Service
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Notification Service
  • Operations manual
  • Start and shutdown
preview 1.32

Start and shutdown

The lifecylce of the container is managed by Kubernetes. The container itself is stateless, therefore it can be shutdown or restarted at any point in time if a downtime is acceptable.

If the container is shutdown or restarted, any events that are currently processed are dropped.

Graceful shutdown

A graceful shutdown helps the application finishes ongoing tasks before it stops.

When you stop the application, it waits for a set time before shutting down. This wait time is controlled by a variable HostSettings__ShutdownTimeoutSeconds, which defaults to 30 seconds but can be changed.

Exit codes

After shutdown, the application will exit with a code to show what happened. These codes help you or support teams understand how the app stopped:

  • None (0) – The application shut down cleanly with no issues.

  • Timeout (1) – Shutdown exceeded the configured timeout (e.g., 30 seconds) before tasks could finish.

  • ShutdownError (2) – An error occurred while shutting down, such as a failure in resource cleanup.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses