# Can you write to Bubble log from Server-side plugin?

**URL:** <https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168>\
**Category:** Questions\
**Created:** [March 29, 2019, 7:16pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168 "2019-03-29T19:16:32Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kfawcett](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/kfawcett/32/38097_2.png) [@Kfawcett](https://forum.bubble.io/u/Kfawcett)\
**Post date:** [March 29, 2019, 7:16pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/1 "2019-03-29T19:16:32Z")

</div>

@Bubble, is there a way to write to the log while developing a server-side plugin?

---

<div class="post-metadata">

**Author:** ![emmanuel](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/emmanuel/32/27657_2.png) [@emmanuel](https://forum.bubble.io/u/emmanuel)\
**Post date:** [March 30, 2019, 1:26pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/2 "2019-03-30T13:26:05Z")

</div>

Well the execution of the action, with the values of the different fields, will be registered in the logs, like any other action that happens server-side.

---

<div class="post-metadata">

**Author:** ![kevin4](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/kevin4/32/59688_2.png) [@kevin4](https://forum.bubble.io/u/kevin4)\
**Post date:** [May 15, 2020, 2:16pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/3 "2020-05-15T14:16:38Z")

</div>

@Kfawcett and @emmanuel

Did you ever get a suitable answer? I’m converting an Element Action into a Server Side Plugin Action and I’m very accustomed to using console.log to monitor the execution sequence of and variable manipulation within a process. Have you found a way to do this in bubble?

---

<div class="post-metadata">

**Author:** ![vini\_brito](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/vini_brito/32/22187_2.png) [@vini\_brito](https://forum.bubble.io/u/vini_brito)\
**Post date:** [May 15, 2020, 2:35pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/4 "2020-05-15T14:35:46Z")

</div>

Errors and the returned object (if any) are logged to the console, so that’s a thing.  
Apart of that, you can return whatever you want as a variable in the result object and/or send the stringified valued to an API (backend workflow) in Bubble or in requestbin for example.

Happy Bubbling! 😄

---

<div class="post-metadata">

**Author:** ![andersan](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/andersan/32/17330_2.png) [@andersan](https://forum.bubble.io/u/andersan)\
**Post date:** [May 15, 2020, 8:03pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/6 "2020-05-15T20:03:25Z")

</div>

The way I usually handle this is by adding a “log” text return, and have one long log message returned by the plugin… another way to do it would be having a “logs” list of texts so that they’re separate.

Can we see console.log() messages in the server logs? I think maybe when the input to the workflow is really long (e.g. has some long text) I think that the console.log output is not visible - maybe that’s why I thought it was never visible.

---

<div class="post-metadata">

**Author:** ![spencer3](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@spencer3](https://forum.bubble.io/u/spencer3)\
**Post date:** [November 1, 2021, 11:35pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/7 "2021-11-01T23:35:46Z")

</div>

Has anyone been able to see server logs? console.log(“PRINT”) does not show up in my logs of a server side plugin I am building.

---

<div class="post-metadata">

**Author:** ![vini\_brito](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/vini_brito/32/22187_2.png) [@vini\_brito](https://forum.bubble.io/u/vini_brito)\
**Post date:** [November 1, 2021, 11:51pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/8 "2021-11-01T23:51:54Z")

</div>

Yes! It works exactly like this:

> [@New plugin making course with all-included and no-knowledge-spared \[15 July 2021\]](https://forum.bubble.io/t/new-plugin-making-course-with-all-included-and-no-knowledge-spared-15-july-2021/160156/16):
>
> In some cases you will be able to use console.log(). This is how it goes:
> 
> ```auto
> function(properties, context) {
>    
> // any code
>    
> console.log("hello server log")
>    
>    
> // any other code
> }
> 
> ```
> 
> You get this here:
> 
> ![image](https://us1.discourse-cdn.com/bubble/original/3X/1/5/153565dc860e708cd73a555018197a4408b0c575.png)
> 
> Note the last log with plenty of information, the logged info is right at the “INFO” section.  
> Good old logging.

You can find more info [here](http://forum.bubble.io/t/new-plugin-making-course-with-all-included-and-no-knowledge-spared-15-july-2021/160156/16), that is just a part of a larger post I wrote 😊

---

<div class="post-metadata">

**Author:** ![spencer3](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@spencer3](https://forum.bubble.io/u/spencer3)\
**Post date:** [November 2, 2021, 3:13am UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/9 "2021-11-02T03:13:08Z")

</div>

Hey Vinny- I did try that exact code but my server log is entirely empty. Do I need to do something to enable logs to show?

---

<div class="post-metadata">

**Author:** ![spencer3](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@spencer3](https://forum.bubble.io/u/spencer3)\
**Post date:** [November 2, 2021, 3:50am UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/10 "2021-11-02T03:50:12Z")

</div>

![image](https://us1.discourse-cdn.com/bubble/original/3X/c/1/c139779cdd3e6a499c6cff765af1cc081c473c3e.png)

---

<div class="post-metadata">

**Author:** ![spencer3](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@spencer3](https://forum.bubble.io/u/spencer3)\
**Post date:** [November 2, 2021, 3:51am UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/11 "2021-11-02T03:51:07Z")

</div>

![image](https://us1.discourse-cdn.com/bubble/original/3X/3/c/3cb894e4c9e01c77be8348a863b771343f20329e.png)

---

<div class="post-metadata">

**Author:** ![vini\_brito](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/vini_brito/32/22187_2.png) [@vini\_brito](https://forum.bubble.io/u/vini_brito)\
**Post date:** [November 2, 2021, 3:12pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/12 "2021-11-02T15:12:05Z")

</div>

@spencer3  
Let’s troubleshoot:  
1 - Write “ten minutes ago” at the first field and “now” at the second;  
2 - Make sure the other fields, “user email” and “contains” are empty;  
3 - Check all boxes in the advanced field;  
4 - Press “Search” button **again** 30 seconds after you run the server side workflow action;  
5 - Make sure the test version of the plugin is installed in the app, it will be in the editor URL, something like `&test_plugin=1543086664409x454646894723334140_current` only that the ID will be different.

Let me know if these helped 😋  
Also, what plan is your app on? You can message me that privately if you want.

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [January 24, 2022, 8:22pm UTC](https://forum.bubble.io/t/can-you-write-to-bubble-log-from-server-side-plugin/53168/13 "2022-01-24T20:22:46Z")

</div>

@vini_brito, I just wanted to note that I came across your replies in this thread while working on an SSA plugin for the first time in forever and found them very useful! I had sort of forgotten where to go to _find_ console logs from SSAs (turning on the Advanced options is, of course, essential here), and further, I had a derpy bug in some new code and just reading another developer’s troubleshooting steps helped put me in the right frame-of-mind to fix the issue.
