This topic was automatically generated from Slack. You can find the original thread here.
Hello. We have been running Pipedream for the Failed Snowflake task for a few weeks now. It seems to have been working well, but today we realized that we missed a notification for one of the failed tasks. How can we troubleshoot this issue? Thanks.
Hello , the fits step to troubleshoot your issue I think is to check if your Snowflake source has emitted event correctly. You can access your workflow Deploy UI and search for the event of the failed task.
If the event is not there, maybe you need to access the Pipedream source log to check for error. To do this, you can access Pipedream source page, select your Snowflake source, then switch to the Logs tab (image below) to search for any error
Finally you can find the error, please submit a ticket for Pipedream, stating all the information you have for us to reproduce
How far back should the log go?
Maybe until the time of the missed failed task occured
So I can only see the log going back 3 days
Oh, so the missed event for the failed task occurred longer than 3 days back?
yes, corrrect
Is it still happening now?
No, it was just one task
Actually, it seem that there is more than one
Hmm then I think it quite hard to troubleshoot now, as the log might get flushed already. Maybe you can setup a workflow for your errors, so that when error occurred in your workflow, you can set custom action to handle it, maybe sending a Slack message, or record it somewhere
Ok. I will give it a day or 2 and will post it again. Thanks
Thanks , please let me know if you have more questions
I suspect there may be something wrong with the logic we’re using. I added some notes to this master ticket, where I also linked a couple of other requests you made, and I prioritized this with the team. You can follow that ticket for updates.
I now have logs and failed tasks. Something is definitely not right. Is it possible to get some assistance on this ASAP? Thanks.
yes, it’s at the top of our backlog right now. Someone should be on it ASAP.
It appears that the problem started after I changed the triggers to run every 6 hours instead of every 15 minutes.
Could this be the issue?
