# Current item is not passed as a context to the workflow

**URL:** <https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156>\
**Category:** Ask for Help\
**Created:** [January 27, 2026, 10:53am UTC](https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156 "2026-01-27T10:53:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DianaT](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@DianaT](https://community.glideapps.com/u/DianaT)\
**Post date:** [January 27, 2026, 10:53am UTC](https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156/1 "2026-01-27T10:53:50Z")

</div>

Hello experts

Can you explain the following behavior - is it a bug or an intended scenario?  
If it is intended - what’s the logic behind?

I can define the Actions in Items in the Collection.  
For example - I need a Delete action.

The inconsistency is when I call this action for a specific item, as on the screen.  
If I call an action - it works on the actual row as expected  
But if I activate a Workflow for this action - it does not pass the actual item as the context row to the workflow. An the workflow runs on an arbitrary selected row.

Is it an expected behavior? or it a bug?

Many thanks  
Diana

 ![Screenshot 2026-01-27 114416](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/c/4c847fa9bb8a001c78b24882f59f41351da069d9.jpeg)

---

<div class="post-metadata">

**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\
**Post date:** [January 27, 2026, 11:09am UTC](https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156/2 "2026-01-27T11:09:18Z")

</div>

Are you using the right trigger? User interaction?

---

<div class="post-metadata">

**Author:** ![DianaT](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@DianaT](https://community.glideapps.com/u/DianaT)\
**Post date:** [January 27, 2026, 11:21am UTC](https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156/3 "2026-01-27T11:21:36Z")

</div>

I suppose yes.

The workflow is triggered for the Delete action in the Item menu

if I check details in the workflow - it shows the details for some another item (i suppose the first row in the table)

I found a workaround for my specific case but this behaviour just looked suspicious )

D

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [January 27, 2026, 3:04pm UTC](https://community.glideapps.com/t/current-item-is-not-passed-as-a-context-to-the-workflow/86156/4 "2026-01-27T15:04:58Z")

</div>

> [@DianaT](#):
>
> But if I activate a Workflow for this action - it does not pass the actual item as the context row to the workflow. An the workflow runs on an arbitrary selected row.

You have to pass a context to the workflow (I assume you’re triggering a manual workflow). In most cases, this should be the rowID, then you do a loop to find that row and delete the row.

Though, you shouldn’t do that, just use the Delete Row action on a user-triggered workflow like you have done.