<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f3886a54d0e3415d9e3db6cc8223ae7f&quot; frameborder=&quot;0&quot; width=&quot;1738&quot; height=&quot;1303&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1303</height><width>1738</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1303</thumbnail_height><thumbnail_width>1738</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f3886a54d0e3415d9e3db6cc8223ae7f-19baa2e7c88053b1.gif</thumbnail_url><duration>98.2625</duration><title>Template Functionality Issues</title><description>In this video, I wanted to share some insights about a template I&apos;ve been working with. I encountered some issues when applying the template, particularly with JSON prompts and outputs. I believe the problem arises from how the template interprets the JSON format. Please take a look at this and see if you can identify the issue.</description></oembed>