Does Pipedream Data Stores Support Transactions or Atomic Operations to Prevent Race Conditions?

21

ah ok, so that won’t help.

22
23

This seems like a huge minefield for end users that won’t be thinking about this stuff

24

maybe the simple solution is to warn them to set workers to 1 if they use data stores

25

otherwise, especially on low volume apps the race condition will be hiding there and when it happens nobody will even know

26

Do you have any other suggestions for how I can do this now, without a race condition?

27

Even a solution without Data Stores would be better

28

Thanks for the feedback. It seems users assume that it’s transactional (and I understand)

29

especially because it’s called a key value and the name of the action is append, that kind of implies atomic action

30

Roughly how many invocations do you expect to receive in a given time frame?

31

I want to count our lead capture action, visitor to my site fills a form and it runs the action. These happen randomly, sometimes very close together. I want to know how many times the trigger was called.

32

Originally I looked for an API that would tell me the number of invocations.

33

Just wondering re: the data store limits

34

handfuls of times

35

Are you in the Basic or Advanced plan?

36

I’m on a legacy plan

37

The solution I’m thinking is write a row for every invocation. Then get the count of rows

38

in a data store?

39

Yep

40

yeah could do that and maybe hit our max