Skip to main content

Action logs

Learn how to view your action's execution history.


To view the run history of an action,

  1. Go to your app's Actions tab and find the action you want to see logs for.

  2. Select Run history option.

Action logs

  1. You can view the list of your action's executions in the opening page.

Action run history

Filtering logs

Click Filter button at top left and select the option(s) to filter by time or filter by status.

Action logs filtering

Filter by time

You can select between below options:

  • Last hour
  • Last day
  • Last week
  • Last month

Filter by status

You can select between below options:

  • Successful: Indicates that the action is run successfully.
  • Partially successful: Indicates that one of the request or functions added to the action's run steps failed. It means that any request or function added before that step is succesful.
  • Stopped: Indicates that the first request or functions added to the action's run steps failed.

Filter by source

You can select between below options:

  • Workflow: Indicates that action is triggered by a workflow.
  • Browser: Indicates that action is run in Actioner through action bar or by testing the action in design mode.
  • Slack: Indicates that action is run in Slack.

Action logs details

Once you select an entry, you can see details of

  • Inputs to run the action and the Action context.

Action logs inputs

  • Requests and functions of the action in the order they are added to the run steps. You can switch between Request and Response tabs of API requests to see their details. Both the request and the response contains header and body objects.

Action logs run steps

Action context detailed

  • app object contains the id of the app the action belongs to.

Example data:

"app": {
"id": "d864feaf-e8b1-4ab0-9114-1c40a45147a2"
}
  • request object contains the requests sent to run the action. Only the requests that are added to run steps are added to action context. Response to API requests contain header and body.

Example data:

"request": {
"CreateJiraIssue": {
"response": {
"headers": {
"Content-Type": [
"application/json;charset=UTF-8"
],
"Date": [
"Wed, 21 Dec 2022 14:43:55 GMT"
],
},
"contentLength": -1,
"body": {
"id": "10035",
"key": "REQ-22",
"self": "https://actioner-demo.atlassian.net/rest/api/3/issue/10035"
},
"statusCode": 201
},
"metrics": {
"durationMillis": 705
}
},
"MessageToRequester": {
"response": {
"message": {
"text": "Nice work! Your request is created :raised_hands:",
"threadTs": "1671633828.018229",
"ts": "1671633835.906279"
},
"channel": {
"id": "C04GPGP4X32"
},
"team": {
"id": "T04FK9CRR8X"
}
}
}
}
  • input object contains the list of input component and the values they took when the action is run.

Example data:

"input": {
"summary": "test",
"channel": "C04GPGP4X32",
"description": "test",
"messageTs": "1671633828.018229"
}
  • workspace object contains the subdomain of the Actioner workspace.

Example data:

"workspace": {
"subdomain": "actionerdemo"
}
  • context object contains the data added to action's run context.

Example data:

"context": {
"key": "value"
}
  • store object contains the data added to app's storage.

Example data:

"store": {
"key": "value"
}
  • user object contains the email and the ID of the user who run the action. If the action is automatically run due to a workflow triggering it, user object is empty.

Example data:

"user": {
"id": "45ff8440-fd42-4d66-aca5-1ebb506052g5",
"email": "joe@actioner.com"
}
  • auth object contains the authentication parameters of any connection referenced by the requests in the action. No sensitive data such as password or API token is disclosed here. They are are shown as hashed.

Example data:

"auth": {
"timeZone": "US/Eastern",
"externalId": "23005198"
}