# Archive of action log

**URL:** <https://community.auth0.com/t/archive-of-action-log/197960>\
**Category:** Get Help\
**Tags:** other, tenant-logs-other\
**Created:** [March 9, 2026, 3:24pm UTC](https://community.auth0.com/t/archive-of-action-log/197960 "2026-03-09T15:24:48Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![olpa](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/olpa/32/77750_2.png) [@olpa](https://community.auth0.com/u/olpa)\
**Post date:** [March 9, 2026, 3:24pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/1 "2026-03-09T15:24:48Z")

</div>

To debug my workflow I do “console.log(…)” in actions. How can I get these messages?

So far I found two ways, which don’t work for me:

- Monitoring → Action Logs, but: it’s a real-time stream, I can’t get the messages from the past
- Monitoring → Logs → Completed login operation → Details → Action Executions, but: because of some bug in the custom workflow (on my side, not yet reproduced), the operations don’t finish either successfully or with an error, so there is no entry in the logs

Where should I look?

---

<div class="post-metadata">

**Author:** ![JFoxUK](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jfoxuk/32/78058_2.png) [@JFoxUK](https://community.auth0.com/u/JFoxUK)\
**Post date:** [March 9, 2026, 3:29pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/2 "2026-03-09T15:29:13Z")

</div>

Hi there,

You could try using this [Actions Real-time Logs - Auth0 Docs](https://auth0.com/docs/customize/actions/actions-real-time-logs)

---

<div class="post-metadata">

**Author:** ![olpa](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/olpa/32/77750_2.png) [@olpa](https://community.auth0.com/u/olpa)\
**Post date:** [March 11, 2026, 5:52am UTC](https://community.auth0.com/t/archive-of-action-log/197960/4 "2026-03-11T05:52:43Z")

</div>

Unfortunately, it’s a real-time stream, I can’t get the messages from the past. Or do I miss something?

---

<div class="post-metadata">

**Author:** ![JFoxUK](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jfoxuk/32/78058_2.png) [@JFoxUK](https://community.auth0.com/u/JFoxUK)\
**Post date:** [March 11, 2026, 7:28am UTC](https://community.auth0.com/t/archive-of-action-log/197960/5 "2026-03-11T07:28:22Z")

</div>

I don’t think you can. You should look to stream out to a SIEM

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 16, 2026, 4:15pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/6 "2026-03-16T16:15:57Z")

</div>

HI @olpa

Welcome to the Auth0 Community!

What kind of trigger are you using to log into the console?

Any console log should definitely be visible under the **Action Executions** tab. In the context of a PostLogin Trigger, it will be visible under the `Successful Login` log and it should look like this:

 ![image](https://global.discourse-cdn.com/auth0/original/3X/6/2/62e5c44f1dcc608c932925eb642f82c6d852d3a3.png)

Once these have been logged, you can use any available log streaming implementation to have them forwarded to an external log management system.

If you can provide me an example on how you are performing this console log, I will be able to provide more information to what the issue might be!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![olpa](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/olpa/32/77750_2.png) [@olpa](https://community.auth0.com/u/olpa)\
**Post date:** [March 17, 2026, 1:51pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/7 "2026-03-17T13:51:03Z")

</div>

Hi @Nik!

My action is of the following structure:

```auto
exports.onExecutePostLogin = async (event, api) => {
  ...
  console.log('debug', whatever);
  ...
  api.redirect.sendUserTo(MY_ENDPOINT, { ... });
}

exports.onContinuePostLogin = async (event, api) => {
  ...
}

```

I get sporadic issues, sometimes the workflow breaks on my side between “sendUserTo” and “onContinuePostLogin”, so for Auth0 the workflow status is probably “hanging” rather than “successful” or “failed”, and the login event is not recorded. And if there is no event, then there is no its “action executions” tab.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 17, 2026, 4:17pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/8 "2026-03-17T16:17:18Z")

</div>

Thanks for the info, I will look into this and come back with an update!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 17, 2026, 4:48pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/9 "2026-03-17T16:48:17Z")

</div>

Hi again @olpa

After some testing, I noticed that you are redirecting the user during the `onExecutePostLogin ` block. As mentioned in our [documentation](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/redirect-with-actions#start-a-redirect):

> Actions will finish the execution of this Action, and then suspend the actions pipeline to send the user to the `https://my-app.exampleco.com`. In other words, any Actions that are bound to the post-login triggers that run after the Action invoking the redirect will not execute until the authentication flow has been resumed. If you are familiar with Redirect Rules, then note that this is a key difference between Redirect Actions and Redirect Rules.

From the information above, if you do not redirect the user back to the `/continue` endpoint, the authentication flow is never fully executed and any other code you have in the initial block will not complete, hence the console log not being visible in the logs (most probably because the `Successful Login` is also absent.

You can either redirect the user inside the `onContinuePostLogin ` block in order for the console log to run or move any relevant code here after the authentication flow is being resumed. That fully depends on what you are looking to accomplish inside the Action, without seeing all the code, I cannot recommend a proper flow for your specific use case.

I would recommend reading more about that [here](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/redirect-with-actions#resume-the-authentication-flow).

Hope the information above is useful, if you have any other questions, let me know!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![olpa](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/olpa/32/77750_2.png) [@olpa](https://community.auth0.com/u/olpa)\
**Post date:** [March 19, 2026, 1:39pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/10 "2026-03-19T13:39:27Z")

</div>

I’m debugging an existing flow like [GDPR: Track Consent with Lock - Auth0 Docs](https://auth0.com/docs/secure/data-privacy-and-compliance/gdpr/gdpr-track-consent-with-lock) , “Option 3: Redirect to another page”. The code on our side has to run before the flow is finished. Sometimes the flow is broken and I’m investigating why, and the information what was done in an action is important here.

Meanwhile I decided that an action will send debug messages to a log collector. Probably it’s actually the best solution.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [March 23, 2026, 5:33pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/11 "2026-03-23T17:33:08Z")

</div>

> Meanwhile I decided that an action will send debug messages to a log collector. Probably it’s actually the best solution.

This would be the best course of action since the redirect stops the console log from completing(however, it does run when using the real time Action Logs) until the user is redirected back as mentioned above. In other words, any code inside the trigger will be completed but for the logs to show the needed information, the user needs to be redirected back to the `/continue` endpoint.

Glad I could help and if you have any other questions, let me know!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [April 6, 2026, 5:33pm UTC](https://community.auth0.com/t/archive-of-action-log/197960/12 "2026-04-06T17:33:14Z")

</div>

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