Known issues and limitations

The following known limitations to the Box connector that may impact your flows.

  • There is a limit of one Webhook for each of the following items: file or folder, application, authenticated user. After a Webhook is attached to an item, no second Webhook can be attached even if the second Webhook responds to a different trigger event.

  • There is a limit of 1000 Webhooks for an application for a user. To create more Webhooks for a user, create another application or update existing Webhooks to apply to higher levels in the folder tree.

  • Connectors use Webhooks V2 and cannot be created on the root folder with ID 0. See Box.

  • Payload includes an object response and additional context information.

Additional information

  • The Box application re-sends a payload up to 10 times after a notification delivery failure.

  • Deleting a Box application automatically deletes all Webhooks associated with the application.

  • Deleting all active Access Tokens associated with a Webhook will automatically delete the Webhook. This includes Developer Tokens and password resets.

  • If the last successful delivery was 30 days ago and the period between the last successful delivery date and the last trigger date was more than 14 days, the Webhook is automatically deleted.
  • When a Webhook is deleted, Box sends a Webhook payload with the WEBHOOK>DELETED event name to the notification URL. The body of the payload includes the following information:
Copy
"additional_info": {

  "reason": "auto_cleanup"

Removing and restoring files and folders

Users may receive a conflict error message after removing and restoring Box files and folders and changing the status of Workflows flow that contains the Box events.

Problem:

A user makes the following changes to an active Workflows flow that contains a Box event:

  • File or folder that is used in the flow (by ID) is moved to the Box trash bin.
  • Workflow flow is deactivated.
  • File or folder is restored from the Box trash bin.
  • Workflow flow is activated.
  • User receives a 409 Conflict error message.

When the file or folder is moved to the trash bin and then restored, the associated Webhook is also restored. In this case, there is an additional file or folder associated to the Webhook. Box limits the number of files and folders to one per Webhook.

Resolution:

  1. Remove, rather than delete, the restored Webhook.

  2. In the Event card in which the flow failed to activate, specify the file or folder in the Target Item ID field.

  3. Using the Custom API Action card, configure the card to make a call to list all Webhooks.

  4. Locate the ID of the Webhook that is the target of file or folder.

  5. Using the Custom API Action card, make a call to delete the ID of the Webhook.

Related topics

Box connector

About the elements of Okta Workflows

Box API documentation