From 018ac3706b185c7cda098e8f7fd23604d2e35599 Mon Sep 17 00:00:00 2001 From: JohnnyEmbleton Date: Fri, 27 Feb 2026 14:29:25 +0000 Subject: [PATCH] Add troubleshooting section for WA task generation Added troubleshooting instructions for WA task generation, including steps to recreate the table schema if errors occur. --- README.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/README.md b/README.md index ce1be82..877c4af 100644 --- a/README.md +++ b/README.md @@ -59,3 +59,34 @@ Because developing in the preview environment is :poop:. ```bash ./bin/import-camunda-definitions.sh ``` + +## Troubleshooting +1. WA Task Generation + + If WA tasks are not being generated, check your docker logs for message_state_enum errors. If found, run these scripts to recreate the table schema: +``` + drop TABLE public.wa_case_event_messages +``` +``` +CREATE TYPE message_state_enum as ENUM ('NEW', 'READY', 'PROCESSED', 'UNPROCESSABLE'); +``` + +``` +CREATE TABLE public.wa_case_event_messages( + message_id text NOT NULL PRIMARY KEY, + sequence serial, + case_id text NOT NULL, + event_timestamp timestamp, + from_dlq boolean NOT NULL DEFAULT false, + state message_state_enum NOT NULL, + message_properties jsonb, + message_content text, + received timestamp NOT NULL, + delivery_count integer NOT NULL DEFAULT 1, + hold_until timestamp, + retry_count integer NOT NULL DEFAULT 0 +); +``` + +After restarting all the pods you should now see WA tasks being generated. +