You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs/api-platform/reference/policies/decode-jwt-policy). info

> [!NOTE]
> Was this troubleshooting playbook helpful? Please let us know by clicking [Send Feedback]().

## InvalidEmptyElement

### Error message

Deployment of the API proxy through either the Edge UI or Edge management API fails
with this error message:

```
Error Saving Revision
Invalid empty element : policy(policy_name) element(Source)
```

### Example error message

    Error Saving Revision
    Invalid empty element : policy(Decode_JWT) element(Source).

### Example screenshot

In the Edge UI, you will see a dialog box with an error:

![](https://docs.apigee.com/static/api-platform/images/decodeJWT-deploy-error.png)

### Cause

This error occurs if the flow variable containing JWT that is to be decoded
is not specified in the `<Source>` element of the DecodeJWT policy.

For example, the error will occur if the `<Source>` element does not contain a
value, as shown below:

    <Source></Source>

### Diagnosis

1. Identify the name of the DecodeJWT policy and name of the element that is empty from the error message. For example, in the following error message, the name of DecodeJWT policy is `Decode_JWT` and the element name is `Source`.

   ```
   Invalid empty element : policy(Decode_JWT) element(Source).
   ```
2. Examine the DecodeJWT policy and verify if the element identified in Step 1 is empty. If the element is empty, then that's the cause of the error.

   Here's a sample DecodeJWT policy:

       <DecodeJWT name="Decode_JWT">
           <DisplayName>JWT Decode HS256</DisplayName>
           <Source></Source>
           <IgnoreUnresolvedVariables>false</IgnoreUnresolvedVariables>
       </DecodeJWT>

   Because the `<Source>` element is empty, you get the error:

       Invalid empty element : policy(Decode_JWT) element(Source).

### Resolution

Ensure that the `<Source>` element specifies a valid JWT in a flow variable.

To fix the issue with the sample DecodeJWT policy, you can specify the flow variable containing a valid JWT in the `<Source>` element.

    <DecodeJWT name="Decode_JWT">
        <DisplayName>JWT Decode HS256</DisplayName>
        <Source>var.jwt</Source>
        <IgnoreUnresolvedVariables>false</IgnoreUnresolvedVariables>
    </DecodeJWT>