Delayed overload

Questions and Comments
#1

So i was listening to my custom doing the mwf listening schedule and it was going fine with no recon then after the weekend washout i woke up tired and what i can only describe as an overload sympton,and my results seem to have slowed/stopped as well,im not sure what to make of this

1 Like
#2

Try 3 rest days instead of 2.
2 did too little in my testing compared to at least 3.
3 is not enough to completely solve overload, but it’s better than 2 even when done more frequently.

But for now, take a long early washout. The cycle is done with that level of overload.

2 Likes
#3

Wow well this sucks,only 3 loops in it gave me overload,not sure what to do now

#4

I was listening to full 15 minute loops,i will try cutting down my listening time to 7 minutes

2 Likes
#5

only 3 loops this cycle? that’s rough.

  • are you sure it’s overload?
  • did you take the proper 5 day washout at the end of the last cycle?
  • what does your schedule look like?
#6

Well i woke up tired and groggy like i need extra sleep,i had overload before and this is what it felt like

Also this is my listening schedule

  1. Listen/
  2. Rest/
  3. Listen/
  4. Rest/
  5. Listen/
  6. Rest/
  7. Rest/
  8. Listen/
  9. Rest/
  10. Listen/
  11. Rest/
  12. Listen/
  13. Rest/
  14. Rest/
  15. Listen/
  16. Rest/
  17. Listen/
    Rest/
    Rest/
    Rest/
    Rest/
#7

I tried this for a few cycles. 17 on 4 off.
It was definitely tip-toe-ing on overload.
I took a few precautions back then, I listened to the subs at the end of the cycle right in the morning and started the next cycle with only microloops right before I slept. Even that was still bordering overload that slowly builds up across cycles.

The experiment wasn’t dead though, slapping 3 straight rest days in the middle of the cycle pretty much solved the issue.

So basically just a normal 17 on 4 off, but take 1 listening day off in the middle.

Personally, I won’t run anything above 13 days straight with less than 5 rest days at the end.
Been there, done that.

1 Like
#8

I plan on reducing my listening time to 7 minutes first before changing my listening schedule

1 Like
#9

I‘m doing this exact same rhythm for ten months now. After three of these cycles I add one week of washout and the next time the washout is four weeks.

Looking at my journal, I can tell you that I always, without one single exception, cut down from 15min loops after the third listening day, when I tried to start with full loops. I‘m not doing this anymore. There‘s too much overload building up for me too. So I cut back to 7min per loop and that works just fine.

With the official 21day on/off recommendation I could always feel too much build up at the end of a cycle so that I usually hoped that it would end one or two listening days earlier. That‘s why I switched to the Mo/We/Fr//Mo/We/Fr//Mo/We// rhythm and it works well so far if I avoid full loops. Also I‘m going to do an additional washout whenever I feel I need to do so.

4 Likes
#10

The experiment wasn’t dead though, slapping 3 straight rest days in the middle of the cycle pretty much solved the issue.

This is cool, so like a mini break in between the cycle. I generally feel a slight overload creeping near the end too, so this might be a good thing to try out

1 Like
#11

I just avoid running a cycle for more than 13 days straight nowadays.
From my experience, 15 days is where the “subtle overexposure build up” starts.
17 days is where it definitely becomes noticeable.

No more overload near the end, no more dancing around the amount of rest day & loop length just to accommodate the schedule.
If anything, the results i’m getting are way better since it’s more consistent without the overload near the end.
I can even get away with only 4 rest days at the end if i run 9-11 days in a cycle.

The consistency of not having the overload near the end always beats getting more exposure imo.

2 Likes
#12

It sounds like your exposure time per listen is off and you’re stacking the processing queue. Think of it like every time during a rest day you don’t fully process the sub, the leftover adds on. Eventually it causes a spike in over processing. And like you witnessed it can be very delayed. I’ve encountered this very frequently until I learned how to balance my listening time per loop. I prefer shorter listening times over longer rest periods because I find small consistent exposure better than large chunks I need more time to process but you may be different.

4 Likes
#13

Yeah thats why im reducing my listening down time to 7 minutes

1 Like
#14

I do a MWF only listening schedule myself, and I too have been hit harder during my 2 days off.

It sounds like you’re moving in the right direction by lessening your loop times.

I used to hear it often that your rest days are when the real work begins. The processing time is when the scripting comes to life.

I only do 3 minute loops, and weekends are VERY busy for me upstairs. It’s why I journal more on weekends.

It’s good to know I’m not the only one :wink:

1 Like
#15

My tip for these ZP subs is have a schedule, but expect deviations, as you never know when it hits you. Before on the old techs it was more about exposure all the time…

But, let’s say I do 1 day on and 1 day off for 21 days. Some cycles I might do the full cycle, but the next I might hit a lot of resistance and brain fog on day 17 or something… Then I usually just take a couple of days of and then restart a new cycle. But sometimes i continue the cycle but add in an extra day of rest.

So what I do is I have a general structure and vision for the schedule, but I keep checking in and react to how I’m doing along the way. Being a bit more fluid within and adaptive, but still keeping some guidelines for listening.

2 Likes
#16

In one day?

#17

No,over a perioid of 7 days

Listen
Rest
Listen
Rest
Listen
Rest
Rest

1 Like
#18

Don’t take it personal. What you call overload could actually be deep processing. Focus more on what’s coming up and write it in a personal journal. It is the easiest and most effective “action” one can take to help resolve recon. Try it and see.

14 Likes
Khan Journal 2025 - Subliminalguy
#19

WOW! That seems important. Would you please repeat that?

Thanks! :grin:

#20

Also looks like ill still be getting the full benefits as 15min

How long to get the full script, with the ticket ID #28886:
Hello Lava,

This is Fire.

There is no need to worry about getting the full script. You’re getting the full effects.

Regards,

  • SC Support