Handling Flowable deadletter jobs
Finding and fixing Flowable jobs that ran out of retries: the deadletter table, reading the exception, fixing data or code, moving jobs back for execution, and alerting before users notice stuck processes.
Flowable operations and troubleshooting
Day-two work on running Flowable engines: failed jobs, retries, monitoring endpoints, logging, audit events and the errors that stop an engine from starting.
Configuring Flowable failed job retries
Setting how Flowable retries failing async jobs and timers: the default of three attempts, failedJobRetryTimeCycle expressions, HTTP task retry patterns, and choosing retry windows that match downstream outages.
Monitoring Flowable with the Spring Boot actuator endpoint
Using the /actuator/flowable endpoint for process counts, running instances and completed tasks, exposing it safely, and feeding the data into existing monitoring.
Managing Flowable with JMX
Connecting JMX clients to a Flowable engine: enabling flowable-jmx, the attributes and operations available such as enabling the job executor and deploying definitions, and securing the JMX service URL.
Flowable logging with mapped diagnostic context
Making Flowable logs traceable: SLF4J mapped diagnostic context fields for process definition, instance and execution IDs, log levels for engine packages, and correlating engine logs with application logs.
Flowable event logging for audit trails
Turning on Flowable's database event logger or a custom flusher to stream engine events as JSON to a queue or search store, and how it differs from history tables.
Fixing Flowable database version mismatch errors at startup
Resolving FlowableWrongDbException when the engine and schema versions differ: what triggered it, upgrading the schema safely, mixed-version clusters during rollout, and preventing it in pipelines.
Flowable timers and async jobs not running
Troubleshooting Flowable timers that never fire and async steps that never continue: async executor activation, unlocked jobs, suspended definitions, expired locks after crashes, and clock or time zone issues.
