# Scheduled Actions

## :timer: What are Scheduled Actions?

With the help of the **action scheduling feature**, you don't need to trigger your actions straight away when the main trigger of the activity fires. Instead, you can schedule an activity and **await a specific player engagement** to occur before they are triggered. 

Scheduled Actions are of great use when **setting up a player campaign with multiple and consecutive player engagements**. With the help of this specific feature, you can manage the whole campaign, step by step, in one single activity.

#### :woman\_raising\_hand: User Example:

**24 hour Campaign:** 10 free spins on login and 50 free spins on deposit\
**Communication channels:** SMS and email\
**When:** Today at 12:00 UTC\
**Segment:** X

**Your activity would be set up with the trigger "Send @ 12:00 UTC" to Segment X and include the following four actions:** \
Send Email\
Send SMS\
Credit Bonus (10 free spins)\
Credit Bonus (50 free spins)

**Should we not make use of the action scheduling feature** and run the activity, all these 4 actions would trigger at 12:00 UTC. Meaning, all the players in Segment X would receive an Email, SMS and the 10+50 free spins - **without** **the requested player engagements** on the credit bonus actions.\
\
In order to avoid the free spins to credit, without the intended player engagements, **we simply schedule** the two Credit Bonus actions within the activity. **Learn how to do just this below.** 

## How to Schedule an Action

With every action type, you have the option to set an action schedule. \
\
**These are the simple steps to scheduling an action:**

* Enter the action that you wish to schedule and scroll down to the bottom
* Tick the box "Should the action be scheduled?" in order for the action schedule options to appear
* Select an already existing trigger, according to your needs, or create a new one
* Enter the **validity amount** followed by the **validity period**

![How to schedule an action](https://3654650655-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGrxN2ttYCb8JwJc2TS%2Fuploads%2F6oXYhVWPpkes3N3mBbc2%2FActionScheduling.gif?alt=media\&token=f1b9bc8d-afbd-4ebf-831f-b8770f1c6bb5)

{% hint style="success" %}
:brain: **Note:** The validity period of a scheduled activity starts when the main trigger of an activity fires. 

**Example:** Activity triggers at 12:00 UTC and an activity is scheduled for 24 hours = the validity of the scheduled action will be up until the following day at 12:00 UTC. \
After this, the action will expire and no longer trigger even if the correct criteria are met in terms of player engagement. 
{% endhint %}

{% hint style="info" %}

#### ⏰ Trigger Immediately to Online Players

When scheduling an action with a Login type of trigger, the **Trigger Immediately to Online Players** feature is enabled by default. This feature is based on the [**Player Online State**](https://fast-track.gitbook.io/knowledge-base/~/revisions/BBJ7kTBPFpakOK9wgBgn/the-singularity-model/player-features/player-feature-player-online-state) Player Feature and will trigger the action immediately to any players that are already logged in on the website when the activity fires.
{% endhint %}

{% hint style="info" %}
📆 **Action Scheduling & Translations**

Action Scheduling is set up and managed in the **default action**. Any translations that are added to that action are subject to the action scheduling of the default action. 
{% endhint %}

### ✋  Disable a Scheduled Action

**Please note that it is not possible to make changes to a scheduled action once the main trigger of your activity has been fired.** This is because, upon the main trigger being fired, the scheduled action has already been entered into a queue. 

Should you want to cancel a scheduled action, it needs to be removed from the queue. To do this, please reach out to your Partner Manager for assistance or [**report an incident**](https://fast-track.gitbook.io/knowledge-base/~/revisions/BBJ7kTBPFpakOK9wgBgn/ft-crm/report-a-problem). Please note that actions removed from the queue can not be restored.