Dear Ivy team. At the moment, we're facing the problem with start link ivy is marked as **Persist task on creation** come with some additional data what was set in **customvarcharfield**. We create a trigger in our ivy's database to listen to any changes in `iwa_task` table. We saw that whenever a user starts that ivy link. ivy will insert a new record in table **iwa_task** with a *taskid* but the value for `customvarchar1 is empty`, very quickly after that, ivy also performs another update on the same task to update data for customvarchar. After 2 updates in the iwa_task table, we have the correct data with a task that is created come with customvarcharfield. It works pretty well for single user because the delay time between 2 updates is very short and unnoticeable. But when there are many users are working at the same time, we got the problem. Because each user access the Portal's tasklist at the same time, so they will query the existing tasks in the system. But under some unluckily moment, the task is created (at the first stage without customvarchar) is queried and return to other user's results. Without customvarchar means the task data is not displayed properly. I just wonder is there any way to make "Persist task on creation" is persisted only once with full of data instead of creating an empty task and update data later.later? Thank in advanced.

Dear Ivy team. At the moment, we're facing the problem with start link ivy is marked as **Persist task on creation** come with some additional data what was set in **customvarcharfield**. We create a trigger in our ivy's database to listen to any changes in `iwa_task` table. We saw that whenever a user starts that ivy link. ivy will insert a new record in table **iwa_task** with a *taskid* but the value for `customvarchar1 is empty`, very quickly after that, ivy also performs another update on the same task to update data for customvarchar. After 2 updates in the iwa_task table, we have the correct data with a task that is created come with customvarcharfield. It works pretty well for single user because the delay time between 2 updates is very short and unnoticeable. But when there are many users are working at the same time, we got the problem. Because each user access the Portal's tasklist at the same time, so they will query the existing tasks in the system. But under some unluckily moment, the task is created (at the first stage without customvarchar) is queried and return to other user's results. Without customvarchar means the task data is not displayed properly. I just wonder how can we is there any way to make "Persist task on creation" is persisted only once with full of data instead of creating an empty task and update data later. Thank in advanced.

Dear Ivy team. At the moment, we're facing the problem with start link ivy is marked as "Persist **Persist task on creation" creation** come with some additional data what was set in customvarchar.**customvarcharfield**. We create a trigger in our ivy's database to listen to any changes in iwa_task `iwa_task` table. We saw that whenever a user starts that ivy link. ivy will insert a new record in table "iwa_task" with a taskid **iwa_task** with a *taskid* but the value for customvarchar1 is empty, `customvarchar1 is empty`, very quickly after that, ivy also performs another update on the same task to update data for customvarchar. After 2 updates in the iwa_task table, we have the correct data with a task that is created come with customvarcharfield. It works pretty well for single user because the delay time between 2 updates is very short and unnoticeable. But when there are many users are working at the same time, we got the problem. Because each user access the Portal's tasklist at the same time, so they will query the existing tasks in the system. But under some unluckily moment, the task is created (at the first stage without customvarchar) is queried and return to other user's result. results. Without customvarchar means the task data is not displayed properly. I just wonder how can we make "Persist task on creation" is persisted only once with full of data instead of creating an empty task and update data later. Thank in advanced.

Dear Ivy team. At the moment, we're facing the problem with start link ivy is marked as "Persist task on creation" come with some additional data what was set in customvarchar. We create a trigger in our ivy's database to listen to any changes in iwa_task table. We saw that whenever a user starts that ivy link. ivy will insert a new record in table "iwa_task" with a taskid but the value for customvarchar1 is empty, very quickly after that, ivy also performs another update on the same task to update data for customvarchar. After 2 updates in the iwa_task table, we have the correct data with a task is created come with customvarcharfield. It works pretty well for single user because the delay time between 2 updates is very short and unnoticeable. But when there are many users are working at the same time, we got the problem. Because each user access the Portal's tasklist at the same time, so they will query the existing tasks in the system. But under some unluckily moment, the task is created (at the first stage without customvarchar) is queried and return to other user's result. Without customvarchar means the task data is not displayed properly. I just wonder how can we make "Persist task on creation" is persisted only once with full of data instead of creating an empty task and update data later. Thank in advanced.