@cap-js-community/event-queue - npm Package Versions

v1.7.0 - 2024-10-22

Added

• Added support for defining periodic event schedules using cron expressions, providing more flexible and precise scheduling options beyond simple intervals in seconds. See documentation.
• triggerEventProcessingRedis is a public api now. This can trigger the processing of multiple events via redis.
• The central configuration property publishEventBlockList has been introduced, enabling the option to disable the publication of the event block list to all application instances. The default value is set to true to prevent immediate impact on existing functionality.

Fixed

• do not initialize the event-queue during cds build/compile steps

v1.6.7 - 2024-10-08

Added

• Enhanced the configuration options to specify not only the application name but also the instance index where the event should be processed. See documentation.
• Enable more event publish properties for CDS outboxed service. See documentation.

v1.6.6 - 2024-08-28

Fixed

• In some cases the event broadcasting is delayed if a periodic event can't obtain the processing lock

v1.6.5 - 2024-08-23

Added

• Introduced the retryFailedAfter configuration option, allowing you to specify the interval (in milliseconds) after which failed events should be retried, provided the retry limit has not been exceeded.
• Increased test coverage for fetching authInfo with @sap/xssec

v1.6.4 - 2024-08-14

Added

• [outbox] add option to use defined user for event-queue also for CAP outboxed services

v1.6.3 - 2024-08-07

Fixed

• [openTelemetry] avoid empty traces for persist-event-status
• [openTelemetry] more resilient for finished spans

v1.6.2 - 2024-08-31

Fixed

• pass correct tenant to fetch authInfo

v1.6.1 - 2024-07-30

Changed

• upgrade to @sap/xssec 4
• Testing with cds 8

Added

• Export WorkerQueue for monitoring purposes to provide insights into the running load of the application.
• JSDocs: added addEntryToProcessingMap for EventQueueProcessorBase
• Enhanced Event Processing: Events will continue to be processed even if the initial processing time is exceeded. Events are now broadcast, allowing different application instances to pick them up. The existing worker queue is used to ensure proper load balancing.

v1.6.0 - 2024-07-09

Added

• Added an option to events to specify which application instance should process the event. See documentation.

Fixed

• Avoid issues with not connected CAP service and open events
• fix clear timeout tenant unsubscribe

v1.5.3 - 2024-06-28

Changed

• single tenant performance improvements

Added

• better test coverage for single tenant