Unanswered

Jotform Enterprise trigger is giving this error. Property value ti cannot be null or empty.

(0) Share

Report

Posted on by MF-23101206-0

I had a flow using this connector that was working perfectly fine then yesterday it started giving me this error. I have tried using a different form, a new form, a form from a different space, a new flow with a new trigger and also deleted and recreated the JotForm connection but the error remains. I have no idea what this ti value is or where to find it. I'm assuming its a trigger/api issue and not likely something I could affect anyway though. I attached screenshots showing the error on the flows main page, as well as flow checker and the error it shows when I click on fix error in flow checker. I also noticed it said it had a successful run today but the run history shows the last successful run was on 6/13.

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (0)

Report

Hi @MF-23101206-0

When i look at the jotform connector page I don't see a V2

JotForm - Connectors | Microsoft Learn

I'm not saying its not there, but I don't see it. So just wanted to verify what trigger you are using. as I cannot see it

can you please share it.

Also, you said if you create a new flow, but when you create the new flow are you simply adding all the same stuff?

Have you created one with just the trigger and a simple compose to see if that works.

Was this reply helpful? Yes No
David_MA 12,966 Super User 2025 Season 2 on at

Like (0)

Report

You will need to open a run of the flow that failed and show the action that failed and how it is configured. If the last successful trigger was June 17, why does your image show the last successful run being June 13?

Putting all that aside, you have an action in your flow that is named "When a response is submitted" that contains a value named "ti". According to the error, there is no data in this field, and that is causing the issue. What you need to do depends on a number of things, but it requires seeing your flow and how the action causing the error is configured. Otherwise, I can just tell you to always make sure that whatever "ti" is, that it contains data to avoid the problem. It could be as simple as making the field required in your form so people cannot submit it unless the provide a value.

Was this reply helpful? Yes No
MF-23101206-0 18 on at

Like (0)

Report

@David_MA, Sorry for the delay in getting back to this. I thought the issue had resolved itself, but I just had another failure, or actually in this case the flow didn't trigger at all. While trying to provide the screenshots you asked for, which I pulled from a different copy of the flow, I did notice that the trigger is referencing a form number that is for a clone of the form I was using for testing, but in the 2nd screenshot you can see that the trigger is supposed to look at form 251193139337963. AT this point I can probably delete the clone of the form as I am done testing with it, but I am not 100% sure that will solve the problem. In regards to the error I am getting I have no idea what that ti field thats null is. None of the fields on the form are named ti, I'm assuming it has to be some sort of metadata field maybe.

@Michael E. Gernaey you are looking at the standard jotform connector, I am using jotform enterprise. Attached a picture of the V2 trigger.

Was this reply helpful? Yes No