# Google Drive "Read file" bug?

**URL:** <https://community.activepieces.com/t/google-drive-read-file-bug/3749>\
**Category:** Need help\
**Created:** [April 5, 2024, 4:45pm UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749 "2024-04-05T16:45:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![S\_M](https://community.activepieces.com/user_avatar/community.activepieces.com/s_m/32/616_2.png) [@S\_M](https://community.activepieces.com/u/S_M)\
**Post date:** [April 5, 2024, 4:45pm UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/1 "2024-04-05T16:45:37Z")

</div>

Instead of getting the **[https://cloud.activepieces.com/api/v1/step-files/signed?](https://cloud.activepieces.com/api/v1/step-files/signed?)…** URL sent in an outgoing HTTP request, I’m getting the URL saved as **file://step\_9/Add to Cal.ics** (Add to Cal.ics is the file name)

 ![image](https://community.activepieces.com/uploads/default/original/2X/0/056067dd24e9a27669757f702c67737dc4b3fa77.png)

---

<div class="post-metadata">

**Author:** ![S\_M](https://community.activepieces.com/user_avatar/community.activepieces.com/s_m/32/616_2.png) [@S\_M](https://community.activepieces.com/u/S_M)\
**Post date:** [April 6, 2024, 1:08am UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/2 "2024-04-06T01:08:18Z")

</div>

To add more context: I’m sending another URL in the HTTP request (non AP link) and it’s being picked up fine

---

<div class="post-metadata">

**Author:** ![abuaboud](https://community.activepieces.com/user_avatar/community.activepieces.com/abuaboud/32/7285_2.png) [@abuaboud](https://community.activepieces.com/u/abuaboud)\
**Post date:** [April 6, 2024, 1:49am UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/3 "2024-04-06T01:49:07Z")

</div>

Hi @S_M,

I understand the confusion, but this is intended; the reason we don’t store any data during production runs is because we only do that for “Testing.” It must be stored to be used to test other steps.

So runs after publishing, it will not generate URLs. You should try to upload it to a storage service or send it as base64 in the http.

---

<div class="post-metadata">

**Author:** ![S\_M](https://community.activepieces.com/user_avatar/community.activepieces.com/s_m/32/616_2.png) [@S\_M](https://community.activepieces.com/u/S_M)\
**Post date:** [April 6, 2024, 2:02am UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/4 "2024-04-06T02:02:01Z")

</div>

Awe okay, thanks for the clarification! I had no clue, first time I was actually trying to use one of those links outside of AP.

---

<div class="post-metadata">

**Author:** ![S\_M](https://community.activepieces.com/user_avatar/community.activepieces.com/s_m/32/616_2.png) [@S\_M](https://community.activepieces.com/u/S_M)\
**Post date:** [April 6, 2024, 12:59pm UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/5 "2024-04-06T12:59:50Z")

</div>

Me trying to use an alternative: [[Dropbox] Bug! The temporary file link action doesn't work](https://community.activepieces.com/t/dropbox-bug-the-temporary-file-link-action-doesnt-work/3769)

---

<div class="post-metadata">

**Author:** ![system](https://community.activepieces.com/uploads/default/original/1X/f3af8cd75e0cc52ac7f19a3b45663ce0396f5016.png) [@system](https://community.activepieces.com/u/system)\
**Post date:** [April 7, 2024, 1:00pm UTC](https://community.activepieces.com/t/google-drive-read-file-bug/3749/6 "2024-04-07T13:00:10Z")

</div>

Closed on April 7, 2024, 1:00pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
