# Gatling EL not working in extracting value from session attribute

**URL:** <https://community.gatling.io/t/gatling-el-not-working-in-extracting-value-from-session-attribute/4467>\
**Category:** Gatling (Open-Source)\
**Created:** [August 27, 2018, 8:30pm UTC](https://community.gatling.io/t/gatling-el-not-working-in-extracting-value-from-session-attribute/4467 "2018-08-27T20:30:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Radha\_Krishna\_Kanth](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@Radha\_Krishna\_Kanth](https://community.gatling.io/u/Radha_Krishna_Kanth)\
**Post date:** [August 27, 2018, 8:30pm UTC](https://community.gatling.io/t/gatling-el-not-working-in-extracting-value-from-session-attribute/4467/1 "2018-08-27T20:30:31Z")

</div>

I have a test that has a scenario with two executions.

1. The first execution is a custom execution that I extended Gatling with
2. The second execution is a standard http execution

What I want to do is set the return value from the first execution as a session attribute to be used in the second execution

The second execution looks like this

```auto

val sfViewGroupingCallExec = exec(http("ViewGrouping Call")
 .get("htps://somecustomurl")
 .header("Authorization","${jwttoken}")
 .check(status.is(200))

```

```auto

```

```auto
I can confirm that if I replace "${jwttoken}" with "${jwttoken.exists()}", 

```

```auto
then the call proceeds and is working since I get a 401 response from the server as expected

```

```auto

```

```auto
However using "${jwttoken}" in the header always gives me "No attribute named jwttoken" response.

```

```auto

```

```auto
I put a breakpoint as far as in NettyRequestSender to see what is the request on the wire and I see that the ${jwttoken} did resolve to a correct value.

```

```auto
So I am not sure why I am getting this error.

```

```auto

```

```auto
Thanks,

```

```auto
Radha.

```

```auto

```