https://linen.dev logo
j
OneDriver trigger events don't seem to fire despite setting active triggers in the UI. I add / remove / move onedrive files and I don't see any trigger event logs...
u
Hey @jparker, could you share the triggerId? It'll help us in debugging.
j
ti_1oDa4zKtWA4w
ti_3sVHShAe-55r
ti_lJx5DHi-rtqN
ti_r2cnn32J8k5h
subscribing to a few to try to capture a 'sync' like lifecycle
@Uday
u
@jparker, We tried it on our end and were able to get payloads for a few One Drive triggers. Could you make sure the events (created, renamed, etc.) are done in the configured directory (folder path)? https://cdn.discordapp.com/attachments/1463864323201040456/1463945483176116234/Screenshot_2026-01-22_at_22.43.04.png?ex=697b95f9&is=697a4479&hm=5b2dc98792ec17f71f4a46dc98665e730230f3433dd294e86e9fd619e07045f4&
j
@Uday where you using the full graph api path or the relative... 1. Relative path: /Documents/MyFolder 2. Full Graph path: /drive/root:/Documents/MyFolder
u
Hey @jparker, it should work fine with Relative path.
j
@Uday weird... i wonder if tis a shared folder issue or something... From claude: Based on the errors and my research, here's what I found: The !sc prefix in DCD5C39F030A442B!sc7b7b6444bdc49e2916f089a06ca9f5d indicates this is a SharePoint container or shared folder, which has different limitations with Microsoft Graph's delta API. According to https://learn.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_delta?view=odsp-graph-online:
"ti_Q2JUkXtUQ2ZE"
u
@jparker, looks like the trigger you've provided has empty config. Could you share more details on how you are creating a trigger?
j
@Uday ... i created that one as a test to try avoid any root folder issues so i din't provdie a trigger config... const triggerConfig = subscription.config as Record; const composioTrigger = await this.ctx.composio.triggers.create( entityId, subscription.triggerId, connectedAccountId ? { connectedAccountId, triggerConfig } : { triggerConfig }, );
My trigger set up is working fine for google-drive but one-drive seems to not work...
u
I see, we were unable to reproduce the issue and seems like there's no issue with the trigger creation. Also, I've noticed 32 triggers for your connected account and I can see 2 successful payloads. Could you try creating a new connected account with a fresh trigger and lmk?
j
@Uday ok, i deleted the account and then reconnected and added the triggers back... still no events on creating or deleting from my onedrive...
I cannot see any events coming through on the composio UI
@Uday unfortunately still not gettign any events coming through composio no matter what I try... google-drive is working smoothly... i would expect to see them in the logs UI given a trigger exists... what underlying service is being used and I can try research the limitation on it to see if onedrive is even firing it to composio?
u
Hey @jparker, Really sorry for the delay. We tried all possible cases on our end and were unable to reproduce the issue. I understand that this is quite frustrating, but could you consider a final request from my end and please share a screen recording of the following: 1. Create a new authConfig and connect an account. 2. Create a
ONE_DRIVE_FILE_CREATED_TRIGGER
trigger for the connected account. 3. Try executing
ONE_DRIVE_ONEDRIVE_CREATE_TEXT_FILE
to create a new file and trigger the file created trigger. 4. Check if you are getting any payloads. 5. Share the trigger Id. Thanks!
j
No problem man. Super appreciative of the support. Would love to get this resolved... Here is the video walking through the flow... https://www.loom.com/share/878f1c2bed5e4fffb246800b5d835792
trigger ids: ti_hZg13dIYE7Uv, ti_OjolCHV5md-F, ti_X7FXmLyFy5Dm, ti_A2t6AKN4OSt2
u
Hey @jparker, Thanks for the loom. It was super helpful. I looked up your connected account Id and it looks like you received a payload (
log_O-vLMizd9iOn
) for file creation. Since OneDrive Toolkit has polling triggers, the payloads are received post the configured interval time (1 min by default). Also, regarding the changes made locally (Finder), there could be an issue with the drive sync. Could you try testing the triggers on browser itself and lmk if there's an issue?
2 Views