You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check if the next state is also wait until, then skip a upsertSearchAttribute as clearing up for the current one(because the next one will be upserting )
Note: this will need a new version after #453 if not built within.
Similarly, we could do the same thing for ENABLED_FOR_ALL -- we can check whether or not it has a next state.
Also, if there is no changes to the StateIds, do not call the UpsertSearchAttribute API
Also make sure the state failed case is covered
The text was updated successfully, but these errors were encountered:
longquanzheng
changed the title
Optimize executingStateIdMode of ENABLED_FOR_STATES_WITH_WAIT_UNTIL
Optimize executingStateIdMode of ENABLED_FOR_STATES_WITH_WAIT_UNTIL and ENABLED_FOR_ALL
Oct 17, 2024
Check if the next state is also wait until, then skip a upsertSearchAttribute as clearing up for the current one(because the next one will be upserting )
Note: this will need a new version after #453 if not built within.
Similarly, we could do the same thing for ENABLED_FOR_ALL -- we can check whether or not it has a next state.
Also, if there is no changes to the StateIds, do not call the UpsertSearchAttribute API
Also make sure the state failed case is covered
The text was updated successfully, but these errors were encountered: