> ## Documentation Index > Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt > Use this file to discover all available pages before exploring further. # Skip one queued send > Skips one queued send: the row is marked `skipped` and the contact's sequence ADVANCES to its next step, with the following step's wait measured from this row's scheduled time. That is what separates skip from decline, which stops the contact's sequence outright. Only a row still waiting to go out can be skipped (`scheduled`, `approval_required` or an action-required row); skipping an already skipped row succeeds again and changes nothing. Only sends belonging to campaigns you own can be skipped; anything else answers 404. Rate limit: 30 requests/minute and 1,000/day per token owner, shared by every campaign, scheduled-send, campaign-template and knowledge-hub endpoint. Errors: - `404` `SCHEDULED_SEND_NOT_FOUND` — No queued send with this id exists, or its campaign is outside your reach. - `409` `SCHEDULED_SEND_NOT_SKIPPABLE` — The send is already settled (sent, stopped, overwritten, replied or failed) and cannot be skipped. - `422` `VALIDATION_FAILED` — sendId is not a 24-character hex id. - `429` `RATE_LIMITED` — More than 30 campaign requests in a minute, or 1,000 in a day, for this token owner (the bucket is shared by every /business/campaigns, /business/scheduled-sends, /business/campaign-templates and /business/knowledge-hubs call). - `500` `UNEXPECTED_ERROR` — An unhandled failure; the detail stays in our logs and is never returned. Requires one of the following token scopes: campaigns. ## OpenAPI ````yaml /openapi.json post /business/scheduled-sends/{sendId}/skip openapi: 3.1.0 info: title: Fuse Business API version: 1.0.0 description: >- External API for lists, campaigns, prospect search and contacts. Authenticate with your API token as HTTP Basic. All paths are under /api/v1. servers: - url: https://api.tryfuse.ai/api/v1 description: Production security: - basicAuth: [] tags: - name: Lists - name: Custom columns - name: Smart columns - name: Exports - name: Campaigns - name: Knowledge hubs - name: Analytics - name: Website intent - name: Account - name: Prospect search - name: Campaign steps - name: Scheduled sends - name: Campaign templates - name: Agents - name: Research - name: Company search - name: Saved searches - name: Folders - name: Contacts paths: /business/scheduled-sends/{sendId}/skip: post: tags: - Scheduled sends summary: Skip one queued send description: >- Skips one queued send: the row is marked `skipped` and the contact's sequence ADVANCES to its next step, with the following step's wait measured from this row's scheduled time. That is what separates skip from decline, which stops the contact's sequence outright. Only a row still waiting to go out can be skipped (`scheduled`, `approval_required` or an action-required row); skipping an already skipped row succeeds again and changes nothing. Only sends belonging to campaigns you own can be skipped; anything else answers 404. Rate limit: 30 requests/minute and 1,000/day per token owner, shared by every campaign, scheduled-send, campaign-template and knowledge-hub endpoint. Errors: - `404` `SCHEDULED_SEND_NOT_FOUND` — No queued send with this id exists, or its campaign is outside your reach. - `409` `SCHEDULED_SEND_NOT_SKIPPABLE` — The send is already settled (sent, stopped, overwritten, replied or failed) and cannot be skipped. - `422` `VALIDATION_FAILED` — sendId is not a 24-character hex id. - `429` `RATE_LIMITED` — More than 30 campaign requests in a minute, or 1,000 in a day, for this token owner (the bucket is shared by every /business/campaigns, /business/scheduled-sends, /business/campaign-templates and /business/knowledge-hubs call). - `500` `UNEXPECTED_ERROR` — An unhandled failure; the detail stays in our logs and is never returned. Requires one of the following token scopes: campaigns. operationId: skipScheduledSend parameters: - name: sendId in: path required: true description: >- The queued send's id (the _id of a GET /business/campaigns/{campaignId}/scheduled-sends row, 24-character hex ObjectId). schema: type: string description: >- The queued send's id (the _id of a GET /business/campaigns/{campaignId}/scheduled-sends row, 24-character hex ObjectId). responses: '200': description: Success headers: RateLimit-Limit: schema: type: integer description: Requests permitted in the current window. RateLimit-Remaining: schema: type: integer description: Requests remaining in the current window. RateLimit-Reset: schema: type: integer description: Seconds until the current window resets. content: application/json: schema: type: object properties: send: type: object properties: id: type: string status: type: string enum: - approval_required - scheduled - sent - skipped - stopped - overwritten required: - id - status required: - send example: send: id: 6a8da7adafc401ca94530e14 status: skipped '400': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '402': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '500': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' security: - basicAuth: [] components: schemas: Error: type: object properties: error: type: object properties: code: type: string message: type: string param: type: - string - 'null' doc_url: type: - string - 'null' request_id: type: - string - 'null' required: - code - message required: - error securitySchemes: basicAuth: type: http scheme: basic description: >- Your API token (`af_…`) as the Basic-auth username, with an empty password. ````