How to Solve 'EMFILE: Too Many Open Files' Error Triggered by WF Sent Gmail Emails Every 15 Minutes?

Help
1

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

Hello there! Could you possibly suggest any solution for this issue I have, please?
The trigger for WF is sent Gmail emails (every 15 mins).

Error: EMFILE: too many open files, scandir '/tmp/__pds__'
    at Object.readdirSync (fs.js:1048:3)
    at module.exports (/var/task/node_modules/rmrf/index.js:5:20)
    at clearScriptTemp (file:///var/task/lambda_handler.mjs:410:3)
    at Runner.runUserCode (file:///var/task/lambda_handler.mjs:856:13)
    at Runner.run (file:///var/task/lambda_handler.mjs:698:12)
    at Runtime.handler (file:///var/task/lambda_handler.mjs:914:48)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

I can provide the WF link and access if necessary.
Thanks in advance :heart:

image.png
image.png753×341 10.3 KB

2

Hi , could you share a screenshot of your trigger?

3

Sure! There it is!

image.png
image.png1208×1009 41.8 KB

4

could you share screenshot of the step having error?

5

It happened 4 times only (1 error is not related to this issue). This WF works fine mostly.

It’s the trigger step, as far as I see. Shared the 2nd SS as well.

image.png
image.png862×1067 74.6 KB

image.png
image.png2274×1184 92.9 KB

6

Thanks , I will check this with Pipedream component dev

7

Should I wait for a bit, then you’re gonna contact me here in this thread?

8

please considering this an asynchronous communication, meaning don’t wait for the response. I will ping you when there’s an update on this, but it won’t be immediate

9

Yeah, I got you. Thanks :slightly_smiling_face:

10

Hey , did it only happen in that sequence? Or were there any other times too?
Can you try replaying the event and see if the error happens again?

11

Hey! I am almost sure it happened in this particular wf only. I’ve restarted all the 4 executions, and it worked fine this time.

However, I wanted to make sure that it is some kind of a corner-case / container error and I do not need to manage Execution controls.

What’s your opinion?

image.png
image.png673×827 25.8 KB

12

Looks good to me!
Let us know if anything pops up again!

13

Alright. Let’s keep an eye on this one.
Appreciate your help!

14

@U03CXTHK4RF Hello there! Faced this issue again.

image.png
image.png889×651 44.3 KB

15

It’s happened more than 20 times.
Also, the trigger has been created on the 28th, but it is processing not the new emails only, but it is processing the emails sent on the 27th and 26th as well.

16

We noticed that the error might be showing up due to the high volume of emails you receive in a short period of time. It’s definitely needing an improvement in the component code. Let me try to reproduce to confirm the suspicion

17

Sure! I’m looking forward to the reply from your side.

18

Hi , thanks for you patience. I took this to the core team and will come back to you when I have a response. Note that they are out of office today due to the holiday in the US.

19

I noticed there is an update available for the Gmail source. Can you try making a copy of the workflow (as a backup), update the trigger version in the new workflow and deploy it? The updated code might help resolve the issue, but no guarantees. Note that if you don’t pause 1 workflow, your consumed credits will be doubled.

20

Hi! It seems that there were no issues during the past couple of days. I’ll take a look at my logs and update the trigger if there will be any issues, same to these we used to have.

For now, I’d just like to get any comments from the core team of your :з
So to say, I do believe that there will be a possibility to perform some specific actions, as soon as we get a response from them.