Skip to content

Commit 77e05bd

Browse files
authored
Update index.md Source Disabled After 14 days Without Enabled Destinations
Source Disabled After 14 days Without Enabled Destinations
1 parent e460727 commit 77e05bd

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/connections/sources/index.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,9 +214,19 @@ To create a source:
214214
4. Enter a name for your source as well as any information on the setup page.
215215
5. Click **Add Source**.
216216

217+
Once the source has been created, the source will automatically be enabled and can begin receiving events immediately, which can be viewed in that source's [Debugger](https://segment.com/docs/connections/sources/debugger/) tab.
218+
> warning "Source Disabled After 14 Days Without Enabled Destinations"
219+
> If a source has no destinations connected or only has disabled destinations connected, then after 14 days Segment will automatically disable this source, even if the source is still receiving data. When a source becomes disabled it will also stop receiving data.
220+
> This event will be visible within your workspace's [Audit Trail](https://app.segment.com/goto-my-workspace/audit-trail) as `Event : Source Disabled` with the details of `Actor : Segment`.
221+
> Workspace's members will receive an email notification prior to the source becoming disabled in order to allow your team to take action.
222+
> If you would like to prevent this behavior of automatically disabling a source even when no enabled destinations are connected, pleaase fill out [this form](https://airtable.com/appADTobzkv0FYLbi/shr7V9LFDZh31cYWW).
223+
217224
> info "One source or multiple sources?"
218225
> Segment suggests that you create one source for each type of data you want to collect. For example, you might have one source for all of your website tracking and a different source for any mobile tracking. Creating one source per data type provides the following benefits:
219226
> - Debugger ease of use - mixing libraries/sources on a single API key means you’re heavily reliant on filtering to actually test events
220227
> - Flexibility sending data to different projects - if you want to have different warehouse schemas, analytics projects, etc, having multiple sources would create this separation
221228
> - More control - as your account grows with the number of destinations you enable, having separate sources allows you to have more control
222229
> - A source type cannot be changed after it is created. You must create a new source if you would like to use a different source type.
230+
231+
232+

0 commit comments

Comments
 (0)