Skip to main content
donaldo71
donaldo71
Silver ⭐️⭐️
April 8, 2026
Question

Loss of formatDateFrom attribute during PutSQL failure retry in Apache NiFi

Hi,

I'm having a problem with a NiFi flow. I use UpdateAttrubute processor when I create an attribute like this: 

formatDateFrom      ${dateFrom:format("yyyy-MM-dd")}
After this I have a PutSql processor that changes a status in DB. When everything is fine, it is ok. However, when something is wrong with the change, this status and my flow go to retry this attribute formatDateFrom disappears and is no longer present in the flow.

Why does this happen and how can I secure this attribute? Attributes created with EvalueateJsonPath didn't disappear, only those created with UpdateAttribute.

5 replies

MattWho
Titanium ⭐️⭐️⭐️
MattWho
Titanium ⭐️⭐️⭐️
April 8, 2026

@donaldo71 I am trying to follow your flow description here and am not very clear.  Can you share your flow definition and indicate where you are seeing the failure. 
What version of Apache NiFi are you using?

You have an UpdateAttribute processor that has its success relationship routed via a connection to the PutSQL processor.  How is putSQL configured?

When "something is wrong", what exception is being thrown in the nifi-app.log?

The more detail you can provide the better chance. community member may be able to provide guidance and suggestions.

Thank you,
Matt

Translate
donaldo71
donaldo71Author
Silver ⭐️⭐️
April 8, 2026

I mean that if the PutSql processor is unable to change the status, e.g. due to the database being unavailable, and the flow goes to the retry path to retry the process, then the attributes I created earlier in UpadetAttribute disappear from the process.This is my values in PutSql processor:

Support Fragmented Transactions
false
 
Database Session AutoCommit
false
 
Transaction Timeout
30 sec
 
Batch Size
50
 
Obtain Generated Keys
false
 
Rollback On Failure
false
 
 

 

Translate
MattWho
Titanium ⭐️⭐️⭐️
MattWho
Titanium ⭐️⭐️⭐️
April 8, 2026

@donaldo71 

It would be helpful to know the full Apache NiFi version being used so I can see if there are any known issue that align here.

I assume that you have a prepared SQL statement configured in your PutSQL processor that uses NiFi expression language to insert values from the Source FlowFile's attributes?

Are you saying that on the very first failed execution of a "retry" routed FlowFile (the attempt that still had the "formatDateFrom" attribute set, there was no exception different from all subsequent retry requests made with FlowFile now missing that attribute)?

Thank you,
Matt

Translate
Terms & ConditionsAccessibility statement