Does the GraphQL Call Correctly Set the "provisionedConcurrency" Variable to 1?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

i inspected the graphql call, it does set the variable correctly “provisionedConcurrency”: 1

2

Can you share here the workflow URL? Happy to look asap

3
4

Many thanks in advance Andrew!

5

Thanks, can you enable support access in your project settings?

6

Looking for it now

7

access granted

8

Is the delay you noticed from Telegram → Pipedream trigger or Pipedream workflow execution → Pipedream workflow completion?

9

it takes about 6 seconds from for the trigger to register on the workflow (spinning wheel appears on the eventlist). It takes another 3 seconds before the first action runs.

I think when the workers are warm, these two steps take around 2-3 seconds total.

10

The biggest sign that the workers are not warm is that my credits usage are not changing. It’s the same. I expect it to increase by 5 every 10 minutes.

11

i believe this used to work fine. I started noticing the issues when pipedream changed its billing system.

12

maybe that has something to do with it.

13

all of sudden, my credits stopped increasing. Maybe pipedream stopped my warm workers so I don’t accidentally run up a large bill under the new plan

14

Interesting, thanks for providing the additional info!

15

Have you tried disabling the configuration, deploy, enable, deploy again?

16

how do i do so?

17

turning off warm workers?

18

Yes

19

i did, i also tried increasing it to 2, 3 workers

20

Ok, thanks