Running queued jobs for API requests

Certain API requests will generate queue jobs that are normally run asynchronously. When using the web interface, the queued jobs are run via ajax. The reason we do this is to prevent potentially slow tasks from holding up the interface. The same problem applies to API requests - if an update to an issue generates lots of email notifications and the SMTP server is running slowly, you would notice a slowdown if the jobs were running inline.

For API requests, you have two options.

  1. Run queued jobs inline with the API request.
  2. Queue the jobs and run them by calling the /queue API method.

The first option is enabled by default. You can change your preference in Settings - General Settings.