Bug Report: Template API Generating Incorrect Page Setup from Traditional to Traditional (Fluid)

·Feb 02, 2026 05:58 PM·

I am seeing a bug with the template API where the page setup is set to Traditional but sometimes it is generating it with Traditional (Fluid) page setup

5 comments

· Sorted by Oldest

Max J.
·
·
Hey Greg! 👋 Thanks for flagging this. To help me dig into what's happening here, a few quick questions:
1.
Is this happening with one specific template or across multiple templates?
2.
Any pattern you've noticed? Like certain prompts, content types, or times when it switches to Traditional (Fluid) vs when it stays on Traditional?
3.
Can you share a gammaId and the prompt from a specific request where it switched? That would help me reproduce it on my end.
4.
When you say the template is set to Traditional, is that the page setup you see when you open the template in Gamma before making the API call?
If you're able to grab a couple of request bodies (one that works correctly and one that doesn't), that would be super helpful for tracking down what's triggering the switch. Let me know!
Greg
·
·
Greg
·
·
thank you.
1.
We are only using 2 templates, I have only seen it happen with 1 of them
2.
No pattern
3.
g_wtfiz1n7zoj7x4k, see prompt above
4.
Yes, the template is Traditional, but then the presentation created is sometimes Default
Max J.
·
·
Thanks for the extra context, Greg! I dug into the recent generations from template g_wtfiz1n7zoj7x4k and found your recent ones. The tricky part is that without seeing a specific generated presentation where the bug happened, I can't compare what went wrong vs what went right. Here are a few of your most recent generations from that template - if any of these show the "Default" page setup instead of "Traditional", let me know which one and I can investigate what happened during that specific generation:
https://gamma.app/docs/th3t9vp68h6j49d (Feb 2)
https://gamma.app/docs/zu1quvuapipmy9y (Feb 2)
https://gamma.app/docs/cx5jc2xor8hc969 (Feb 1)
Or if it's a different generation, just drop the gammaId of the generated presentation (the one showing the bug) and I'll track it down from there. Thanks for your patience - once I can see a specific failing example, I should be able to figure out what's causing the inconsistency!
Greg
·
·
ok thanks if i see it again I will let you know

Max J.
·
·
Hey Greg! 👋 Thanks for flagging this. To help me dig into what's happening here, a few quick questions:
1.
Is this happening with one specific template or across multiple templates?
2.
Any pattern you've noticed? Like certain prompts, content types, or times when it switches to Traditional (Fluid) vs when it stays on Traditional?
3.
Can you share a gammaId and the prompt from a specific request where it switched? That would help me reproduce it on my end.
4.
When you say the template is set to Traditional, is that the page setup you see when you open the template in Gamma before making the API call?
If you're able to grab a couple of request bodies (one that works correctly and one that doesn't), that would be super helpful for tracking down what's triggering the switch. Let me know!
Greg
·
·
Greg
·
·
thank you.
1.
We are only using 2 templates, I have only seen it happen with 1 of them
2.
No pattern
3.
g_wtfiz1n7zoj7x4k, see prompt above
4.
Yes, the template is Traditional, but then the presentation created is sometimes Default
Max J.
·
·
Thanks for the extra context, Greg! I dug into the recent generations from template g_wtfiz1n7zoj7x4k and found your recent ones. The tricky part is that without seeing a specific generated presentation where the bug happened, I can't compare what went wrong vs what went right. Here are a few of your most recent generations from that template - if any of these show the "Default" page setup instead of "Traditional", let me know which one and I can investigate what happened during that specific generation:
https://gamma.app/docs/th3t9vp68h6j49d (Feb 2)
https://gamma.app/docs/zu1quvuapipmy9y (Feb 2)
https://gamma.app/docs/cx5jc2xor8hc969 (Feb 1)
Or if it's a different generation, just drop the gammaId of the generated presentation (the one showing the bug) and I'll track it down from there. Thanks for your patience - once I can see a specific failing example, I should be able to figure out what's causing the inconsistency!
Greg
·
·
ok thanks if i see it again I will let you know