# Error messages to info.html.erb
**URL:** https://discourse.openondemand.org/t/error-messages-to-info-html-erb/3829
**Category:** Get Help
**Created:** [October 23, 2024, 9:49pm UTC](https://discourse.openondemand.org/t/error-messages-to-info-html-erb/3829 "2024-10-23T21:49:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@pakalee](https://discourse.openondemand.org/u/pakalee)
#### Post date: [October 23, 2024, 9:49pm UTC](https://discourse.openondemand.org/t/error-messages-to-info-html-erb/3829/1 "2024-10-23T21:49:11Z")
What would be a good way to place any errors that occur during startup in a batch connect session into the session card?
One idea would be to simply output the `output.log` from a session within info.html.erb
Any other more robust ways?
Creating an error file and outputting that to the session card? How do I access the staging dir files or the session ID files from within my info.html.erb ?
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [November 12, 2024, 9:11pm UTC](https://discourse.openondemand.org/t/error-messages-to-info-html-erb/3829/2 "2024-11-12T21:11:50Z")
I think that’s about as good as you can get. I feel like `staged_root` should be available to these ERBs (that’s the directory location ending in the UUID of that job).
---
### Author:  [@system](https://discourse.openondemand.org/u/system)
#### Post date: [May 11, 2025, 9:12pm UTC](https://discourse.openondemand.org/t/error-messages-to-info-html-erb/3829/3 "2025-05-11T21:12:29Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.