PutDatabaseRecord not writing new columns after schema changes

Summary

PutDatabaseRecord loads the database table schema only when the processor starts. If the table schema changes while the processor is running, it will not detect new columns until it is restarted.

Symptom

• New columns do not receive values

• Incoming records contain the new fields, but database rows do not

• No errors appear, but data is missing

• Changes to table structure seem ignored

Root Cause

• PutDatabaseRecord caches the table schema at startup

• Schema is not refreshed automatically

• Adding new columns (for example column c) does not update the cached schema

• The processor continues using the old schema with only a and b

How to Fix It

Restart the processor

Stopping and starting PutDatabaseRecord forces it to reload the table schema from the database.

Steps:

1. Stop processor

2. Start processor again

3. Run flow and verify new columns are written

Optional: restart the process group

If multiple processors rely on the same schema, restart the entire group if easier.