We are facing an issue where record load is happening before we get data back fr

marcg over 8 years ago

We are facing an issue where record load is happening before we get data back from an api call. This is an intermittent issue. We cannot figure out the root cause. We issue http gets then do a put and we are expecting a return set and then a new page should display. The put works, the data is updated in the remote database but our page never refreshes. If we hit the browser refresh button the page looks find and the data we expect back is displayed. We believe the record load happens before the process completes. Any thoughts on resolving the issue? We are using APPIAN 7.8

Discussion posts and replies are publicly visible

Parents

0 PhilB
A Score Level 1
over 8 years ago

Your observation - "We believe the record load happens before the process completes" - is basically correct.

If there's no chaining after a user input task that has been started from a record, and the subsequent flow includes (for example) a database write which should alter the record, you'll be returned to the record before the database write has actually completed, and so will see the "old" version of the data.

Chaining means the user isn't pushed back to the record until after the writes have completed. It does mean that the user waits a little longer, but I guess that's better than seeing the wrong information!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 PhilB
A Score Level 1
over 8 years ago

Your observation - "We believe the record load happens before the process completes" - is basically correct.

If there's no chaining after a user input task that has been started from a record, and the subsequent flow includes (for example) a database write which should alter the record, you'll be returned to the record before the database write has actually completed, and so will see the "old" version of the data.

Chaining means the user isn't pushed back to the record until after the writes have completed. It does mean that the user waits a little longer, but I guess that's better than seeing the wrong information!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data