# Meta
Logux stores metadata for every [action] in separated object:
```js
log = [
[action1, meta1],
[action2, meta2],
…
]
```
Meta contains Logux-related data. It should not contain anything related to application state.
Meta has unique action’s ID, creating time, processing status and many other things. Meta is open structure, applications can set custom keys to meta object.
```js
{
added: 5,
id: "1564508138460 380:R7BNGAP5:px3-J3oc 0",
reasons: ['amplifr/lastPrices'],
subprotocol: 10,
time: 1564508138460
}
```
[action]: ./action.md
## Setting Meta
Most of methods to add action accept meta as second arguments:
```js
store.dispatch.sync(action, meta)
store.commit.sync(action, meta)
client.log.add(action, meta)
server.log.add(action, meta)
ctx.sendBack(action, meta)
```
The only methods without meta argument:
Redux client
`store.dispatch(action)`. Use `store.dispatch.local(action, meta)` to set meta for local-tab actions.
Vuex client
`store.commit(action)`. Use `store.commit.local(action, meta)` to set meta for local-tab actions.
Redux client
```js
store.log.changeMeta(actionId, {
reasons: []
})
```
Vuex client
```js
store.log.changeMeta(actionId, {
reasons: []
})
```
Pure JS client
```js
client.log.changeMeta(actionId, {
reasons: []
})
```
Node.js
```js
server.type('users/rename', {
…
resend (ctx, action, meta) {
return `users/${ action.userId }`
},
…
})
```
Django
```python
class RenameUserAction(ActionCommand):
action_type = 'user/rename'
def resend(self, action: Action, meta: Optional[Meta]) -> List[str]:
return [f"users/{action['payload']['userId']}"]
```
Ruby on Rails
_Under construction. Until `resend` will be implemented in the gem._