For experimentation purpose, I failed a "Write to Data Store Entity" n

charlesb454 over 9 years ago

For experimentation purpose, I failed a "Write to Data Store Entity" node by changing a column in the DB. As expected the node changed to the 'Cancelled by exception' state. After restoring the column I restarted the failed node but it changed to an 'Unattended' state with green border (no new rows in the DB and nothing in the 'stdOut' log file), where I expected the write to proceed normally and the process instance to continue. Anyone has an explanation for that behavior (Additional info: the node writes a nested cdt)?

Thank you!

Discussion posts and replies are publicly visible

0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

Was it working before?
Did you update the CDT to match the table column or updated the table to match CDT?

Try configuring the node again and run to check if it works.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 charlesb454 over 9 years ago

Thanks for answering. Yes, it was working and is currently working on new process instances. My question relates to a running process instance that I want to resume after fixing the problem (table column).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

How many are running and the statuses for each, similar to the attached?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 charlesb454 over 9 years ago

FYI, I found the cause.The process wasn't resuming because someone was monitoring and editing the process instance. The thing resumed once the lock was broken on the instance. Thanks again!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

If you closed the edit mode but it is still paused. Manually pausing the process and resuming works.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 charlesb454 over 9 years ago

Ah, thanks for the tip! (I tried resuming with no success but haven't tried the pause before)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ryanh over 9 years ago

I've found that sometimes the lock isn't released when closing the editing window. Logging out of Appian and back in breaks the lock so you can then resume the process.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel