Episode 35 – Weekly plan exists in DB but workflow fails to detect it when creating posts

[S4KMedia]

Hi,

This issue is about Episode 35 (Instagram Influencer Machine).

The weekly plans ARE correctly saved in the influencer_weekly_plans data table.
I can see multiple entries with the correct:

• influencer_id
• week (e.g. 2025/3, 2025/4, etc.)
• plan text

However, when running the “Create post” flow, the workflow always stops at:
“No plan for this week – You need a weekly plan before creating a post”

What’s happening:

• The weekly plan is successfully created and stored in the DB
• The week selector skips earlier weeks and only shows future ones
• The Get the plan for the week / Has a plan for the week? logic never detects existing plans
• The lookup seems to fail due to week format / mapping mismatch between form input and DB query

So the problem is NOT missing data — it’s the workflow logic that fails to match existing weekly plans.

Could you please clarify:

• What exact week format the workflow expects at post-creation time
• Which node is the single source of truth for the week value
• Whether this is a known bug in Episode 35

Thanks

[S4KMedia]

Hi,
Episode 35 isn’t working for me.

Weekly plans are saved correctly in influencer_weekly_plans, but when creating a post the workflow always says “No plan for this week”.

The “Get the plan for the week” node returns an empty item, so “Has a plan for the week?” always goes false, even though the plan exists (same week, same influencer_id).

Is there something missing or implicit in the workflow setup that’s not shown in the video/repo?

Thanks.

[S4KMedia]

As a result, in “Get the plan for the week” the condition
week = {{$json.week}}
is always undefined, so it always returns false even when weekly plans exist in the DB.

Looks like the selected “Select week” form field is not mapped into the Create post branch.

[macko01-cyber]

I have the same problem, identical situation. Was there any way to solve it?

[macko01-cyber]

As a result, in “Get the plan for the week” the condition week = {{$json.week}} is always undefined, so it always returns false even when weekly plans exist in the DB.

Looks like the selected “Select week” form field is not mapped into the Create post branch.

Thanks to your response, I figured out what the problem was — it was with the formatting.
The system was adding the year as 2025/1, etc. I changed it to 2026/1, 2, 3, 4, and so on.
However, the real issue turned out to be that I had to physically update the value in the table to 2026/04, and it’s important to use 04 instead of just 4.