Answers to: Handle error in Waiting element

Comment by ToanLC on Reguel Wermelinger's answer

ToanLC — Tue, 29 Aug 2017 22:45:19 -0400

Hi @reguel-wermelinger I'm just curious as this eventID is just 91 characters. It haven't exceeded the maximum length yet. I think the problem is that the eventID is already exist. And his problem (I think he forgot to mention it) is that he get an error log and an hour or 1/2 hour after he will get another warning log. But he would like to catch the error as soon as it happens.

Comment by ThongNguyen on Reguel Wermelinger's answer

ThongNguyen — Mon, 28 Aug 2017 21:44:30 -0400

Thank for your reminder. I think it just warning. But how about Error Log??

Answer by Reguel Wermelinger

Reguel Wermelinger — Mon, 28 Aug 2017 09:02:47 -0400

Ensure that you use a shorter ID: here you have obiously a length problem:

'SMART_METER_GAETWAY_METER_CREATE_CONFIRMATION_EVENT_ID_005056b0-f842-1ed7-8daa-75acae8f09b2' already exists. The event identifier of an intermediate event element must always be unique! trunkated because it is to long to store in database column which only supports 200 characters

you could shorten the identifier plus use a simpler ID format. Our own ID generator is able to generate shorter unique ids. Just give it a try: ch.ivyteam.util.GuidUtil.generateID()