Pipedream and OneDrive error: "Error: The resource could not be found


I have a workflow that is triggered by a source called OneDrive New File in Folder (Instant).

It has been working for the past few months but stopped working even though the workflow has not been changed.

The Pipedream workflow is no longer being triggered when a file is uploaded to OneDrive.

The source of the workflow is throwing this error:

super(message || (baseError && baseError.message));
Error: The resource could not be found.
at GraphError.GraphError (/var/task/node_modules/@microsoft/microsoft-graph-client/src/GraphError.ts:61:3)
at Function.GraphErrorHandler.constructErrorFromResponse (/var/task/node_modules/@microsoft/microsoft-graph-client/src/GraphErrorHandler.ts:76:18)
at Function.<anonymous> (/var/task/node_modules/@microsoft/microsoft-graph-client/src/GraphErrorHandler.ts:102:31)
at step (/var/task/node_modules/tslib/tslib.js:193:27)
at Object.next (/var/task/node_modules/tslib/tslib.js:174:57)
at /var/task/node_modules/tslib/tslib.js:167:75
at new Promise (<anonymous>)
at Object.__awaiter (/var/task/node_modules/tslib/tslib.js:163:16)
at Function.GraphErrorHandler.getError (/var/task/node_modules/@microsoft/microsoft-graph-client/src/GraphErrorHandler.ts:99:65)
at GraphRequest.<anonymous> (/var/task/node_modules/@microsoft/microsoft-graph-client/src/GraphRequest.ts:391:55)

I cloned the workflow and it works but it is important that this does not happen again.

Does anyone know what the cause of this error was?


Hi @lharney,

In the affected workflow, would you mind accessing your workflow settings, enable Pipedream support to access your workflow. Then send an email to support@pipedream.com, stated your issue with your workflow url?

I believe Pipedream support engineer might be able to debug it

1 Like

Thank you

Hi @lharney, Looking into it, and it appears that is a issue with the webhook subscription expiry. Although the source does renew it automatically every 15 days, so I’ll look deeper into the logs.
One question, I’ve seen that you’ve created this source 6 months ago? That’s interesting, since in the docs it states that the first subscription is set to expire in 6 months.

Hi @lharney, unfortunately we only store roughly the logs for the 100 most recent events. So I’m not able to look deeper into this.

I’ll explain how this trigger works:
This source sends an webhook subscription update every 15 days. What could’ve happened is it failed to send the subscription update, causing it to expire. We’ve recently fixed a bug that involved failing to emit some polling events, so if that was the cause it should not happen anymore.

Your copy of the trigger should work from now on without intervention, but if in case it happens again in ~ 6 months please let us know.

1 Like

Thanks Andrew.

FYI please follow this Github issue for the fix